Event-Driven Architecture – Benefits and Pitfalls
summary
Explains concrete patterns: uses Kafka and Google Pub/Sub for transmission, stores events in an event store as an append-only log with snapshots and log compaction, and implements CQRS plus event sourcing with materialized views. Demonstrates an inventory bug workflow where a wrong "damage 15" event is negated by a contra event then corrected to "damage 5," shows replay/upcasting for versioning, warns about duplicates, lost events, and no single atomic transaction so idempotency and delivery guarantees are essential.
AI-written summary · about
chapters (10)
- 0:00Introduction to EDA
- 1:49What is event-driven architecture
- 6:28Defining events and their types
- 10:46Event versioning and storage
- 16:52CQRS and event sourcing patterns
- 21:11Topologies in EDA
- 24:23Benefits of event-driven systems
- 28:00Pitfalls and challenges
- 36:31Handling consistency and lost events
- 42:52Q&A and resources
related talks
31mDemystifying Event-Driven Architectures
41mGetting started with Event-Driven Architectures in 2023
23mEvent-Driven Architecture: Unleashing responsiveness
43mUnraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture
52mSo You Want to Build An Event Driven System?
01h 08mEvent Driven Architecture – Enabling Microservices
54mSo You Want to Build An Event Driven System?
54mHow Events Are Reshaping Modern Systems