The term โ€œEventโ€ is really overloaded. There are many different utilities that leverage events. Event Sourcing, Event Carried State Transfer, and Event Notifications. None of these are for the same purpose. When talking about an Event Based architecture, realize which one youโ€™re using and for what purpose.

๐Ÿ”” Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1

๐Ÿ’ฅ Join this channel to get access to source code, demos, and slides!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join

๐Ÿ“ Blog: https://codeopinion.com

๐Ÿ“š Book Recommendations

Domain-Driven Design
https://amzn.to/2QwG8sb

Patterns of Enterprise Application Architecture
https://amzn.to/3d8kMJj

Refactoring: Improving the Design of Existing Code
https://amzn.to/2NVdP5Q

Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
https://amzn.to/3srUuZ6

RESTful Web Clients: Enabling Reuse Through Hypermedia
https://amzn.to/3d8Q96B

0:00 Intro
1:10 Event Sourcing
3:03 Event Carried State Transfer
5:38 Event Notifications
8:32 Differences

CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion

#event based architecture #architecture #event

Event Based Architecture: What do you mean by EVENT?
1.25 GEEK