Message Queues vs Event Brokers By David Boyne

EDA visuals and the book is free thanks to our sponsors:

Manage, secure, and govern every API in your organization.

Delivering Apache Kafka professional services to your business.

Message Queue

Messages are put onto a queue and a consumer consumes the message and processes them. Messages are acknowledged as consumed and deleted afterwards. Messages are split between consumers which makes it hard to communicate system with events.

Example of this would be Amazon SQS. Publish messages to the queue and then listen to them, process them and they are removed from the queue.

Event Broker

Event brokers are a push system, they push these events downstream to consumers. Example of this would be Amazon EventBridge.

Extra Resources

Building Event Driven Microservices - Notes mainly from this book by Adam Bellemare

Explore other visuals

Common issues when scaling event-driven architectures

Common problems when going beyond the initial setup of event-driven architectures.

Event Types

Different types of events used in EDA

Splitter Pattern

Taking one event/message and splitting it into many.

Want to work together?

If you're interested in collaborating, I offer consulting, training, and workshops. I can support you throughout your event-driven architecture journey, from design to implementation. Feel free to reach out to discuss how we can work together, or explore my services on EventCatalog.

EDA Visuals: The book

Join over 13,000 others learning EDA and download all the EDA visuals directly to your computer.

This book contains all the visuals in one book, you can download, read offline and explore.

Purchase book $15.00

Purchasing the book supports my work, but for whatever reason if the book is beyond your budget, you can download it for free here.

Purchase book $15.00