KoP (Kafka on Pulsar) brings the native Apache Kafka protocol support to Apache Pulsar by introducing a Kafka protocol handler on Pulsar brokers. By adding the KoP protocol handler to your existing Pulsar cluster, you can migrate your existing Kafka applications and services to Pulsar without modifying the code. This enables Kafka applications to leverage Pulsar’s powerful features, such as:
KoP, implemented as a Pulsar protocol handler plugin with the protocol name "kafka", is loaded when Pulsar broker starts. It helps reduce the barriers for people adopting Pulsar to achieve their business success by providing a native Kafka protocol support on Apache Pulsar. By integrating the two popular event streaming ecosystems, KoP unlocks new use cases. You can leverage advantages from each ecosystem and build a truly unified event streaming platform with Apache Pulsar to accelerate the development of real-time applications and services.
KoP implements the Kafka wire protocol on Pulsar by leveraging the existing components (such as topic discovery, the distributed log library - ManagedLedger, cursors and so on) that Pulsar already has.
The following figure illustrates how the Kafka-on-Pulsar protocol handler is implemented within Pulsar.
The following new features are introduced in KoP 2.8.0.
The following enhancement is added in KoP 2.8.0.
The property name of Kafka listener
listeners is deprecated. Instead, you can use
kafkaListeners since KoP 2.8.0.
Since Pulsar 2.6.2, KoP version changes with Pulsar version accordingly. The version of KoP
x.y.z.m conforms to Pulsar
m is the patch version number.
|KoP version||Pulsar version|
You can configure and manage KoP based on your requirements. Check the following guides for more details.