Apache Kafka vs. JMS Message Broker (IBM MQ, TIBCO, Solace)

This recording is a lot more than a simple compare of technologies, ... thanks for all the real-world project insides!

[@shivanshudubey8832]

It's one of the best apple to orange comparison ever witnessed.

[@walidmatta1]

What do you recommend, KAFKA or ESB in the context of Integrated Manufacturing Operations Management Systems (MOMS) in the oil and gas industry (Refinery)

It depends more on the use case and technical requirements, not so much on the industry. I have a dedicated article (and video) exploring the differences between ESB and Kafka: www.kai-waehner.de/blog/2019/03/07/apache-kafka-middleware-mq-etl-esb-comparison/

[@contactdi8426]

Great explanation! Thanks

[@Purutge]

top content!!

[@joseindi744]

Complete biased comparison, not even in one characteristic is comparing purely one broker with another. The real answer to this comparison is that actually it depends on the use case, if you dont mind to have some messages without being processed go to Streaming messaging that performs awesomly. BUT if you need an Enterprise grade guarantee of the delivery of all the messages, JMS architecture is unbeatable

I don't disagree. If you just need enterprise messaging, then JMS is great (if the message broker can handle the scale you need and licensing cost makes sense). Kafka and JMS usually service different use cases, though you can also leverage Kafka for messaging (but not the other way round). A more detailed comparison based on 10 characterstics is here (but still similar approach as the presentation): www.kai-waehner.de/blog/2022/05/12/comparison-jms-api-message-broker-mq-vs-apache-kafka/