4 Key Types of Event-Driven Architecture

Adam Bellemare compares four main types of Event-Driven Architecture (EDA): Application Internal, Ephemeral Messaging, Queues, and Publish/Subscribe.

Event-Driven Architectures have a long and storied history, and for good reason. They offer a powerful way to build scalable and decoupled architectures. But thanks to its long history, people often have different ideas of what EDA means depending on when they first encountered this architecture.

RELATED RESOURCES

CHAPTERS
00:00 - Intro
00:38 - What are Events and Records?
01:33 - Type 1: Application Internal
02:44 - Type 2: Ephemeral Messaging
04:19 - Type 3: Queues
06:12 - Type 4: Publish/Subscribe
08:25 - Summary

--

ABOUT CONFLUENT

#eventdrivenarchitecture #apachekafka #kafka #confluent #events #messages #topics #queues

[ConfluentDevXTeam]

Adam here. Event-driven architecture (EDA) can mean different things to different people. They can be internal to a single application, a distributed network of asynchronous applications, or a queue of tasks for a worker to process. But these all fall under the event-driven umbrella.

With this video, I wanted to highlight four main types of EDA to illustrate how each type plays a role in building resilient, scalable, and performant architectures.

Let me know what you think of this video in the comments below. Also, would love to hear what topics on event-driven architecture you would like to see covered next!

[oscarluizoliveira]

Congratulations on the content Adam, this area of ​​technology of ours is very complicated, with many of the same terms having different meanings depending on the context, I'm studying postgraduate studies in software architecture and it drives me crazy. Taking advantage, when we talk about an ephemeral form without retention, we are referring to a pattern where events are processed in real time and are not stored for later consultation, is that it?

[artmusic]

cant you use kafka for app internal communication or queues aswell? or is this not recommended?

[maciekskontakt]

Good explanation - not quite correct examples. ESB is not about ephemeral messaging (if you worked with it you would know not from theory - I did for years). Ephemeral is topic related. However, Apache Camel ESB with Apache MQ GUARANTEES delivery even on topic provided that subscriber subscribed once (it is lost in two cases: not subscribed first time or you exceed parameters of how for long it is stored).

[ShimoriUta]

Bro how do you write mirrored like that on glass?

[teolcd]

EDA is by nature the most powerful approach for distributed systems. However, this video is about structure and a bit of behavior pattern. If you need more info, you will need to research QoS, versioning, schema ...