Event-Driven Architecture: I do not think it means what you think it means

With the popularity of Microservices, Kafka, and Event Sourcing, the term "Event" has become pretty overloaded and has caused much confusion about what Event-Driven 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 Event-Driven architecture, such as Event Sourcing, Event-Carried State Transfer, and Events for Workflow. 🔗 EventStoreDB https://eventsto.re/codeopinion 🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1 💥 Join this channel to get access to a private Discord Server and any source code in my videos. 🔥 Join via Patreon https://www.patreon.com/codeopinion ✔️ Join via YouTube https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join 📝 Blog: https://codeopinion.com 👋 Twitter: https://twitter.com/codeopinion ✨ LinkedIn: https://www.linkedin.com/in/dcomartin/ 📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeopinion 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-sourcing-is-hard Event Driven Architecture — 5 Pitfalls to Avoid https://medium.com/wix-engineering/event-driven-architecture-5-pitfalls-to-avoid-b3ebf885bdb1 #softwarearchitecture #softwaredesign #eventdrivenarchitecture