The difference between Messages Brokers, Event Brokers & Event Streams (Kafka vs message brokers)

What are the differences between message brokers and event-brokers and event streaming platforms? And their pros and cons in using them in event-driven architecture.
The following book is a MUST read amzn.to/3mDuBHD Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems (this is a book which I'd recommended for every technical person and has had pride of place for many years on my desk)
This video is NOT sponsored. Some product links are affiliate links which means if you buy something I’ll receive a small commission.
Time Stamps
0:48 - Important points to consider when selecting a message broker for event-driven architecture
1:12 - What is a message broker
2:18 - Pros & Cons of standard message brokers
3:38 - What is a Event broker
3:58 - Log-Based message brokers
4:27 - Introducing Event-Streaming Platforms
6:02 - Pros & Cons of an Event-streaming platforms
#eventdrivensystems #eventdrivenarchitecture #microservices #rabbitmq #apachekafka #awssqs #awssns #azureeventhubs #danieltammadge
Disclosure: Some of the links below are affiliate links. This means that, at zero cost to you, I will earn an affiliate commission if you click through the link and finalize a purchase.
---
I use www.lucidchart... for my diagrams & www.flaticon.com where I use my pro subscription to find images for my content
I have gained my knowledge by watching talks and reading many articles, but more importantly designing, and running event-driven systems in production for many years, along with making many mistakes during that time.
But I think a great place to start is the following two books
Designing Data-Intensive Applications By Martin Kleppmann amzn.to/3c5l2wq (this is a book which I'd recommended for every technical person and has had pride of place for many years on my desk)
And
Designing Event-driven systems by Ben Stopford (This is the best book I have read on event-driven architecture) www.benstopford...
Now a great article on event streaming is an article called "Turning the database inside-out with Apache Samza" www.confluent....
And I would also recommend the book Building Event-Driven Microservices by Adam Bellemare Building Event-Driven Microservices amzn.to/3pz2QOS
Following my experience with event-driven systems, I found Martin and Ben's content to align with what I have experienced and learned, while there are some viewpoints in Adam's book which I don't agree with, it is an excellent book and strove of knowledge with many nuggets of gold in its pages.
Hope you find these books and articles as useful as I have in your journey in event-driven architecture. Just FYI the amazon links are affiliate links (#CommissionsEarned).

[@strahinjagajic8340]

Excellent job with tutorials, your tutorials are spot on :) Please continue to upload quality content. Cheers!

[@Danieltammadge]

Thank you I’m so glad you liked them.

[@theokaralenka]

Very nice tutorial! Straight to the point, well explained, no unnecessary blah-blah. Thanks!

[@Danieltammadge]

Thanks you

[@thomas-sinkala]

Thank you very much, Daniel. Your explanations are clear and straight to the point.

[@Danieltammadge]

Thanks Ikenna. I’m glad you liked the content

[@kristinaribena1654]

Excellent video

[@StephenTD]

Awesome great content

[@Danieltammadge]

Glad you found it useful

[@emmanuellazarte8904]

Hi! MOM (middleware), Hub & Spoke model, Message Broker are all the same? I'm confused about them and EDA and ESB :( I'd try to use the books that you recommend us.

[@Danieltammadge]

I have only recently heard of the "Hub and Spoke Model" in terms of application communication after years of designing solutions with event-driven architecture in the last few months. And in my ignorance, I have not spent time trying to understand the pattern until your comment. However, with a quick google search, and some hours of reading, I found this abstract from the book Architectural Patterns by Pethuru Raj, Anupama Raman, Harihara Subramanian. - "The hub and spoke pattern is a variant of the event broker topology pattern. In the hub and spoke architecture, the hub acts as the centralized broker and the spoke act as adapters that connect applications to the hub. The spoke establishes a connection with an application and converts application data into a format that the hub understands. The hub translates the incoming data into a format that is understood by the destination system and performs routing of messages accordingly. The presence of a single hub makes this architecture easy to manage, but at the same time imposes limits on the scalability of the architecture - From my limited understanding, I think the spoke adds more coupling between components/applications and the hub service, than typical brokers. But that is just my ignorance talking. Please, for everyone reading, comment if you can share insight on this model. Also, I would like to know more about others' experiences and understanding. Now let us look at the middleware. Queuing services, Message Brokers, Event Brokers/Streaming platforms, and Enterprise Service Buses (ESB) are types of middleware, but as you go from a queuing service to a broker, Platform and then to an ESB, The features and functionality you can use increase. Let's take AWS services as examples of some of the different types of middleware they offer. First up, we a simple queuing and notification services like AWS SQS and AWS SNS that provide pub/sub and subscribing without having to set up more complex brokers. Next up, you have brokers, which provide more functionality like routing and filtering, such as Amazon MQ, RabbitMQ and ActiveMQ. Then you have Event Brokers or Event Streaming Platforms (Apache Kafka/AWS MKS) Then you have your ESB, AWS EventBridge, which provides additional functionality like integrating different systems.