Here is a Typesafe/Reactive point of view on the question from Jonas Bonér. From the third paragraph of this blog post: The difference being that messages are directed, events are not — a message has a clear addressable recipient while an event just happen for others (0-N) to observe it.
In traditional message processing, you apply simple computations on the messages — in most cases individually per message. In stream processing, you apply complex operations on multiple input streams and multiple records (ie, messages) at the same time (like aggregations and joins). Furthermore, traditional messaging systems cannot go “back in time” — ie, they automatically … Read more
Kafka uses the abstraction of a distributed log that consists of partitions. Splitting a log into partitions allows to scale-out the system. Keys are used to determine the partition within a log to which a message get’s appended to. While the value is the actual payload of the message. The examples are actually not very … Read more
You can use a transformation broker without a service bus, and vice versa. In terms of specific products I don’t think any one is purely one or the other because of the way each complements the other. Some products are stronger in the one area, other stronger in another. Perhaps a choice needs to be … Read more
We choose Camel over Spring-Integration because the fluent API is really nice. We actually use it in Spring projects and use Spring to configure part of it. The programming API’s are clear and there is a large set of sensible components. We did a small scale shootout and basically at that time for our requirement … Read more
Can I have each consumer receive the same messages? Ie, both consumers get message 1, 2, 3, 4, 5, 6? What is this called in AMQP/RabbitMQ speak? How is it normally configured? No, not if the consumers are on the same queue. From RabbitMQ’s AMQP Concepts guide: it is important to understand that, in AMQP … Read more
A Connection represents a real TCP connection to the message broker, whereas a Channel is a virtual connection (AMQP connection) inside it. This way you can use as many (virtual) connections as you want inside your application without overloading the broker with TCP connections. You can use one Channel for everything. However, if you have … Read more