How Event Driven Architectures Go Wrong & How to Fix Them
summary
Common failures are concrete and fixable: teams ship YOLO events that only carry IDs and force hundreds of consumers to call back, EventBridge delivers at‑least‑once duplicates, a single bloated god event becomes thousands of JSON lines, and simple flows balloon into pinball events (one example uses seven events just to create an order). Practical fixes include an RFC window of a month, recorded ADRs, anti-corruption layer transforms for legacy dumps, using Step Functions for orchestration, and distributed tracing; EventBridge spins up in about 2 minutes so governance must be lightweight but real.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:51What are we trying to achieve with EDA?
- 6:06YOLO events
- 11:18God events
- 15:28(Too) Sparse events
- 16:37Pinball events
- 19:59Leaky domains
- 23:07Inside out events
- 29:24Outro
related talks
48m9 Fallacies of Event driven Architectures
38mEvent-driven Architecture
44mThe Dark Side of Events
52mSo You Want to Build An Event Driven System?
31mDemystifying Event-Driven Architectures
49mJourney to EDA: Patterns, Best Practices & Practical Tips
39mBuilding next-gen applications with event-driven architecture
56mDesigning Event-Driven Applications to Improve Scalability