Message Queues vs Event Brokers By David Boyne

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

Serverless infrastructure for event-driven architecture.

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

Fundamentals of event-driven architecture

Successful event-driven architecture, distilled into three main areas

Message Queues vs Event Brokers

Understanding queues and pub/sub

What is Event Sourcing?

Bite sized visual to help understand the Event Sourcing.

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.

Download EDA Visuals

Join over 10,000 others learning EDA and download all the EDA visuals directly to your computer. This document updates everytime a new visual is added so make sure you come back to get the latest.

Download now →