Kafka
Apache Kafka
Judgement: Adopt
The streaming backbone; competitors challenge the implementation, not the category.
Distributed log and streaming platform. Originally built at LinkedIn, donated to ASF; now the default backbone for event-driven data pipelines.
The Kafka wire protocol is openly documented and re-implemented by Redpanda, WarpStream, and others, so it sits next to AMQP as a standard option for asynchronous data movement.
Why it counts as a standard
The Kafka wire protocol is publicly documented and re-implemented by Redpanda, WarpStream, and AutoMQ — clients written for one server work against the others. The standard surface is the protocol, not the Apache Kafka broker; that is what lets producers and consumers stay portable across vendors.
At a glance
- Category
- Messaging
- Governance
- Apache Software Foundation
- Status
- Stable; the de-facto streaming platform
- First released
- 2011
Links
Related standards
Other standards in Messaging.
- CloudEvents
- AMQP — Advanced Message Queuing Protocol
- MQTT — Message Queuing Telemetry Transport
- JMS — Jakarta Messaging (formerly Java Message Service)
See Kafka in context
Open the interactive Data Landscape to compare Kafka against every other open standard, or grab the raw JSON. Spotted something wrong? Open an issue.