Answer the question
In order to leave comments, you need to log in
Why do you need JMS (RabbitMQ, etc.) if you have Apache Kafka?
Backround: I came across Kafka on the project very superficially, I poked something in the Kafka Tool, sent something, received it, but nothing more. I had nothing to do with RabbitMQ at all.
And so I decided to study the topic in more depth.
Googled, read on the topic.
And here's what is not clear - Kafka seems to be better than the usual JMS, RabbitMQ by all criteria.
The question is: why do we need the old JMS if there is Kafka? Only support legacy?
And what would you recommend to study first? Kafka or start over with JMS?
Answer the question
In order to leave comments, you need to log in
These are fundamentally different products - one is a message queue, and the other is streaming. In Kafka, there is no concept of messages, or rather, the implementation is abstract there. Kafka operates on bytes of information. In addition, Kafka is bad with routing, which is available in other brokers.
So it’s better or worse than dissimilar to compare solely within the framework of choosing a solution for a specific task
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question