Event Stream for dummies

Photo by Joao Branco on Unsplash

Event Stream for dummies


2 min read

Hi guys,

Another sharing today but really cool topic for backend guys out there ๐Ÿ˜‰

I'll share with you the Event Stream and what are the benefits of it. And it could be your next awesome tool besides the normal Queue.

What is an Event Stream?

An event stream is like a river of information that flows continuously and captures all the things that happen over time.

It's like a never-ending sequence of messages that describe different events, such as user actions or changes to data.

An event stream is often used in software systems to help them react and respond to these events in real-time.

Think of an event stream as a way for software systems to keep a constant eye on what's happening and respond accordingly.

A sample diagram here - how services would pub/sub to the Event Stream:

The benefits

The processing

The same processing as normal queues or pub/sub. Your service will need to subscribe to the stream and then process the incoming events (latest ones) ๐Ÿ˜‰

The message availability

Events won't be deleted from Event Stream, your Events are still there for days (based on your need - set the configuration ๐Ÿƒโ€โ™‚๏ธ).

An event stream is designed to maintain a record of all events that occur over time. Each event is added to the stream as it occurs and is not removed from the stream unless explicitly deleted. This allows the event stream to maintain a historical record of all events that have occurred, which can be useful for auditing, debugging, or other purposes.

  • Unlike normal Queues, msgs will be deleted after the processing.

Services can retain the old events (if needed) ๐Ÿ”‹.

  • Unlike normal Pub/Sub, if your service wasn't able to receive the msg, the msg won't be delivered and result in data loss.

The visibility

You are actually can search and see the msgs and their payload.

  • I think this is quite normal, but hell-nah for SQS ๐Ÿซ 

The coding approach

Event Stream can be used as a middleman for communication between services.

  • Good ol' Publisher/Producer - Subscriber ๐Ÿ˜˜

(Optional) Fully Event-driven Architecture for your applications - your microservices โ™ป๏ธ

What platform can I use?

  • Kafka (most popular)

  • GCP Pub/Sub

  • RabbitMQ

  • Solace

  • ...


The event stream is really awesome, isn't it? Especially for those applications that use a fully Event-driven Architecture approach.

The benefits are great, aren't they? It is a great addition to mission-critical applications.

And indeed, I'm using the Event Stream at the moment and totally love it.

Cheers guys!