Hello Marko,
The difference is that the publisher has to know before hand to which queues to
publish. With the AMQ model, you have a more decoupled model: The publisher
only know the Exchange, and the consumers register themselves without the
producer knowing about them. Therefore, let’s say
1. You can create N topics
2. You control from producer where each message goes
3. You have consumer that fetches from M different topics:
https://kafka.apache.org/0100/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html#subscribe(java.util.Collection)
Isn't this architecture flexible
It sounds like you can implement the 'mapping service' component yourself
using Kafka.
Have all of your messages go to one kafka topic. Have one consumer group
listening to this 'everything goes here' topic. This consumer group acts as
your mapping service. It looks at each message, and based on
Hello,
We’re considering migrating an AMQ-based platform to Kafka. However our
application logic needs an AMQ feature called Dynamic Binding, that is, on AMQ
one publishes messages to an Exchange, which can be dynamically configured to
deliver a copy of the message to several queues, based on
