Event Sourcing is seemingly constantly being confused with Event Driven Architecture. In this video I'm going through a popular blog post that explains various points that are very valid, however, they are conflating Event Sourcing with Event Driven Architecture. Event Sourcing is about using events as the state. Event Driven Architecture is about using events to communicate between service boundaries. 🔗 EventStoreDB https://eventsto.re/codeopinion 🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw 💥 Join this channel to get access to source code & demos! null 🔥 Don't have the JOIN button? Support me on Patreon! https://www.patreon.com/codeopinion Oskar Dudycz: Event Streaming is not Event Sourcing! https://event-driven.io/en/event_streaming_is_not_event_sourcing/ Original Blog Post https://chriskiehl.com/article/event-sourcing-is-hard 📝 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 0:58 Event Sourcing is an anti-pattern 5:15 Upstart Costs are Large 6:38 Event Sourcing needs the UI side to play along 7:51 Building two different systems along side each other 9:48 Audit log will often have fidelity problems 10:51 Dealing with materialization lag #eventsourcing #eventdrivenarchitecture #softwarearchitecture