Complexity is the Gotcha of Event-driven Architecture

on YouTube ↗44m

" summary

Event-driven systems deliver agility but inherit rapid, often-hidden complexity as services, brokers and channels scale; expect coupling, unclear domains and schema drift. Practical guardrails are: behavior-first event storming to map domain events before implementing, explicit event evolution strategies (backwards-compatible fields, parallel versions) and consumption rules (anti-corruption layers, conformist vs open host). Use tooling and specs like CloudEvents and AsyncAPI, and catalogue artifacts with Event Catalog (≈17,000 catalogs, ~50 contributors) to regain governance and trace who consumes what.

AI-written summary · about

" chapters (11)

1. 0:00Intro
2. 2:32Agenda
3. 3:53Potential of EDA
4. 11:53Evolution architecture increases complexity
5. 19:05Control complexity with guardrails
6. 22:51Event Storming
7. 25:52Event evolution strategy
8. 31:09Complexity with event consumers
9. 35:50Biggest gotcha of them all
10. 42:09Summary
11. 43:48Outro

" related talks

• 55mNavigating complexity in event-driven architectures: A domain-driven approachDavid Boyne · NDC London 2025
• 52mNavigating complexity in event-driven architectures: A domain-driven approachDavid Boyne · NDC Copenhagen 2025
• 31mThe Power of Event-Driven Systems without Burning your Hands or BudgetsAllard Buijze · GOTOpia November 2020
• 42mDesign Principles for an Event-Driven ArchitectureLuis Garcia, Pablo Ruiz · Commit Conf 2019
• 48mEvent-Driven Architecture – Benefits and PitfallsRamanan Natarajan · Developer Summit 2020
• 46mManaging Event Driven ArchitecturesIan Cooper · Build Stuff 2021
• 48mEmpowering Architectural Evolution: Governing Event-Driven SolutionsSam Dengler · GOTO EDA Day Nashville 2023
• 54mSo You Want to Build An Event Driven System?James Eastham · CPH DevFest 2024