Complexity is the Gotcha of Event-driven Architecture
summary
Argument: event-driven systems deliver big agility gains but complexity quickly erodes value unless actively managed. Specific guardrails: behavior-first event storming instead of implementation-first, explicit event evolution strategies (backward-compatible fields, optional new fields, parallel versions), and coupling patterns (anti‑corruption layers or open host service). Practical tools and outcomes: use EventBridge SQS SNS plus CloudEvents for envelopes, document channels with AsyncAPI and an open-source event catalog (600 people on Discord, ~13,000 entries) to discover who consumes what and avoid breaking changes.
AI-written summary · about
chapters (7)
- 0:00Intro
- 5:08Agenda
- 5:41Potential of EDA
- 21:03Guardrails to manage complexity
- 37:58Biggest gotcha of them all
- 45:04Summary
- 46:30Outro
related talks
48m9 Fallacies of Event driven Architectures
27mEmbracing Complexity in Serverless
52mSo You Want to Build An Event Driven System?
49mJourney to EDA: Patterns, Best Practices & Practical Tips
39mEvents, Workflows, Sagas? Keep Your Event-driven Architecture Sane.
31mDemystifying Event-Driven Architectures
39mBuilding next-gen applications with event-driven architecture
44mThe Dark Side of Events