Event Streaming vs Message Queue
People think event streaming is just a message queue. A queue hands each message to one reader and then removes it. A stream keeps every event for a set time. Many readers can each read all of it, at their own pace, and read it again later.
Event Streaming
Events move between systems as they happen. They are kept so they can be read again.
Event streaming moves events between systems the moment they happen and keeps them in order. An event is a small record, such as a click, a payment or a sensor reading. Producers write events to a stream. Consumers read them, live or later, each at their own pace. Unlike a simple queue, the stream keeps events for a set time, so many readers can use them.
Message Queue
A line where messages wait for a free worker.
A message queue holds messages until a worker is ready for them. They come from one part of a system and go to another. The sender, or producer, drops a message in and moves on. A worker, or consumer, takes messages out one at a time and does the work. Each message is usually handled by just one worker. If workers are busy or down, messages wait safely in the queue.
In one line
- Event Streaming
- Events move between systems as they happen. They are kept so they can be read again.
- Message Queue
- A line where messages wait for a free worker.
These live in different corners of the glossary (Data and Development), which is exactly why they get confused.