Apache Kafka vs. ESB / ETL / MQ

Apache Kafka and Enterprise Service Bus (ESB) are complementary, not competitive!

Apache Kafka is much more than messaging in the meantime. It evolved to a streaming platform including Kafka Connect, Kafka Streams, KSQL and many other open source components. Kafka leverages events as a core principle. You think in data flows of events and process the data while it is in motion. Many concepts, such as event sourcing, or design patterns such as Enterprise Integration Patterns (EIPs), are based on event-driven architecture.

Kafka is unique because it combines messaging, storage, and processing of events all in one platform. It does this in a distributed architecture using a distributed commit log and topics divided into multiple partitions.

ETL and ESB have excellent tooling, including graphical mappings for doing complex integration with legacy systems and technologies such as SOAP, EDIFACT, SAP BAPI, COBOL, etc. (Trust me, you donโ€™t want to write the code for this.)

Therefore, existing MQ and ESB solutions, which already integrate with your legacy world, are not competitive to Apache Kafka. Rather, they are complementary!

Read more details about this question in my Confluent blog post:

Apache Kafkaยฎ vs. Enterprise Service Bus (EBS) | Confluent

As always, I appreciate any feedback, comments or criticism.

Tags: , , , , , , , , , , , , , , , , ,

Leave a Reply

๐Ÿ˜‰ ๐Ÿ˜ ๐Ÿ˜ก ๐Ÿ˜ˆ ๐Ÿ™‚ ๐Ÿ˜ฏ ๐Ÿ™ ๐Ÿ™„ ๐Ÿ˜› ๐Ÿ˜ณ ๐Ÿ˜ฎ mrgreen.png ๐Ÿ˜† ๐Ÿ’ก ๐Ÿ˜€ ๐Ÿ‘ฟ ๐Ÿ˜ฅ ๐Ÿ˜Ž โžก ๐Ÿ˜• โ“ โ— 

What is 15 + 2 ?
Please leave these two fields as-is:
IMPORTANT! To be able to proceed, you need to solve the following simple math (so we know that you are a human) :-)