Seamlessly interface web apps, IoT clients, and microservices to Apache Kafka® via declaratively defined, stateless APIs.
Zilla is a multi-protocol, event-native proxy. Deploy it in front of Apache Kafka® and declaratively define REST, SSE, MQTT & gRPC API entry points that map to Kafka topics & services. Non-Kafka apps & microservices can now directly consume & produce event streams via their own native APIs — no need to deploy and manage custom integration code, Kafka Connect® or any other intermediaries.
For apps and clients that can’t natively interface to Kafka event streams, a combination of Kafka Connect and intermediary web services or brokers is needed. This leads to increased latency, unnecessary data replication, a wider security surface area and an overall disjointed interface to event-driven architectures.
Kafka's performance & resilience benefits extended across the entire application stack.
Heavy Kafka integration middleware replaced by a single, stateless API layer.
Developers across teams accessing event-streams via their own APIs of choice.
Centralized authorization & authentication of all non-Kafka clients.
Use Zilla for application integration, modernization and development.
Interface REST and gRPC services to event-streams with app specific API declarations, enabling them as first-class participants inside an event-driven architecture. Achieve a CQRS event-sourcing design pattern with minimal effort.
Leverage your cluster as an asynchronous backend for web and mobile clients. Build live dashboards, geotracking, in-app chat and more, all without dedicated servers or third-party pub/sub services. Fan out data to millions of clients.
Expose event-streams to external client applications and services, securely and at scale. Go beyond a synchronous HTTP interface for your partner integration strategy.
Reduce redundant replication and lag by connecting MQTT clients directly to Confluent without intermediary MQTT brokers and Kafka Connect.