A snappy open-source proxy for Apache Kafka that enables encryption, multi-tenancy, and schema validation.
Kroxylicious is an open-source proxy for Apache Kafka that intercepts and transforms Kafka protocol traffic between clients and brokers. It solves operational challenges by providing encryption, multi-tenancy, and schema validation without requiring changes to Kafka itself. The proxy acts as a transparent intermediary, enhancing security and manageability in Kafka deployments.
Kafka administrators, platform engineers, and developers managing enterprise Kafka clusters who need to add security, isolation, or validation features. It's also suitable for teams building custom Kafka integrations or extensions.
Developers choose Kroxylicious because it offers a lightweight, extensible way to add enterprise-grade features to Kafka without modifying brokers or clients. Its filter-based architecture allows custom transformations, and it's performance-optimized to minimize latency, making it a practical solution for production environments.
Kroxylicious, the snappy open source proxy for Apache Kafka®
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Adds TLS encryption to Kafka traffic without modifying clients or brokers, addressing a key security use case highlighted in the features.
Enables resource management and isolation for multiple tenants on shared clusters, solving operational challenges in enterprise deployments.
Validates message schemas to ensure data consistency and compliance, a core functionality mentioned in the project's key features.
Supports custom filter development via Maven archetypes, allowing tailored protocol transformations as detailed in the Filter Development section.
Introduces an additional component to deploy, monitor, and maintain, increasing system complexity and management burden compared to native Kafka setups.
While designed as 'snappy', the proxy layer inherently adds latency and potential bottlenecks due to the extra network hop, which may impact high-throughput scenarios.
As a newer project, it has fewer community-contributed filters and integrations compared to established Kafka tools like Confluent Platform or Schema Registry.