AMQP 1.0 - Kafka bridge
An HTTP bridge enabling HTTP 1.1 clients to send and receive messages to/from Apache Kafka clusters.
What is AMQP 1.0 - Kafka bridge?
Strimzi Kafka Bridge is an HTTP bridge that allows HTTP 1.1 clients to interact with Apache Kafka clusters. It solves the problem of Kafka's native proprietary protocol by providing a standard HTTP interface for producing and consuming messages. This enables applications and services that only speak HTTP to seamlessly integrate with Kafka messaging systems.
Developers and architects building systems that need to integrate HTTP-based applications (like web services, legacy systems, or IoT devices) with Apache Kafka for event streaming or message passing.
It provides a simple, standardized way to connect HTTP clients to Kafka without requiring Kafka-specific libraries or protocol knowledge. As part of the Strimzi ecosystem, it offers reliable deployment options on Kubernetes and OpenShift alongside standalone flexibility.
Overview
An HTTP bridge for Apache Kafka®
Use Cases
Best For
- Integrating legacy HTTP-based applications with modern Kafka event streams
- Enabling IoT devices or web clients to publish messages to Kafka topics via HTTP
- Building microservices that need HTTP ingress for Kafka messaging
- Creating proof-of-concept Kafka integrations without Kafka client libraries
- Deploying Kafka connectivity in Kubernetes/OpenShift environments using Strimzi
- Providing RESTful API access to Apache Kafka clusters for non-JVM languages
Not Ideal For
- High-performance streaming applications requiring minimal latency and maximum throughput
- Systems needing advanced Kafka features like exactly-once semantics or Kafka Streams via HTTP
- Environments where Kafka native clients are already deployed and HTTP abstraction adds unnecessary complexity
- Projects requiring modern HTTP protocols like HTTP/2 or WebSockets for real-time communication
Pros & Cons
Pros
Allows any HTTP 1.1 client to connect to Kafka, enabling integration with legacy systems, web services, and IoT devices without Kafka-specific libraries, as highlighted in the README.
Supports amd64, arm64, ppc64le, and s390x architectures, making it deployable on diverse hardware, though the README notes that arm64 and ppc64le are untested.
Integrates seamlessly with the Strimzi Kafka operator for containerized environments on Kubernetes and OpenShift, simplifying orchestration in cloud-native setups.
Provides OpenAPI-generated API references and detailed documentation in the project's docs, ensuring clear interface definitions and ease of use.
Cons
The README explicitly states that arm64 and ppc64le architectures are supported but not tested, posing potential stability issues for production deployments on these platforms.
As an HTTP bridge, it introduces additional latency and processing compared to native Kafka clients, which may bottleneck high-throughput or low-latency use cases.
Only supports HTTP 1.1, lacking modern protocols like HTTP/2 or WebSockets that could improve efficiency and enable more real-time features.
For Kubernetes deployments, it relies on the Strimzi operator, adding vendor lock-in and complexity for teams not already invested in the Strimzi ecosystem.
Frequently Asked Questions
Related Projects
CloudEvents.io Java SDKJava SDK for CloudEvents
Vert.x MQTT ServerVert.x MQTT
The White RabbitKotlin coroutine based library for RabbitMQ
openapi4j adapter for Vert.xOpenAPI 3 parser, JSON schema and request validator.
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.