With the popularity of Microservices, Kafka, and Event Sourcing, the term "Event" has become pretty overloaded and has caused much confusion about what EventDriven architecture is. This confusion has led to conflating different concepts leading to unneeded technical complexity. I'm going to shed some light on different aspects of EventDriven architecture, such as Event Sourcing, EventCarried State Transfer, and Events for Workflow.

EventStoreDB
https://eventsto.re/codeopinion

Subscribe:    / @codeopinion  

Join this channel to get access to a private Discord Server and any source code in my videos.

Join via Patreon
  / codeopinion  

✔ Join via YouTube
   / @codeopinion  

Blog: https://codeopinion.com
Twitter:   / codeopinion  
✨ LinkedIn:   / dcomartin  
Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo...

0:00 Intro
4:56 Event Sourcing
9:48 Data Distribution
16:43 Notifications
23:50 Tooling

Referenced Blog Posts

Don't Let the Internet Dupe You, Event Sourcing is Hard
https://chriskiehl.com/article/event...

Event Driven Architecture — 5 Pitfalls to Avoid
  / eventdrivenarchitecture5pitfallstoavoid  

#softwarearchitecture #softwaredesign #eventdrivenarchitecture