Silence is Coming: Surviving Chaos in a Distributed Event-Driven Architecture
summary
An experience report from AXA France about operating a distributed event-driven architecture (EDA) built by multiple squads using existing tech. It analyzes a systemic failure mode where event streams stop (a “silence” anti-pattern) causing business processes to stall, and prescribes concrete practices: process-oriented observability, explicit producer-consumer contracts, and clear ownership to build resilient, Build-to-Last EDA systems.
AI-written summary · about
chapters (13)
- 0:00Event-driven intro
- 5:01Conformance project
- 9:40Multicultural team silence
- 11:28C4 model for docs
- 17:50C4 governance at AXA
- 19:36Cross-team dependencies
- 21:44Testing risks
- 23:49Monitoring processes
- 26:37Pilot deployment issues
- 29:51Experience feedback
- 34:27Avoiding system chaos
- 36:123 tips for distributed archs
- 38:18Q&A
related talks
51mComplex Event Flows in Distributed Systems
42mApplication Architectures: The shadows and highlights of Event Driven Design
50mDo Distributed Systems they said. It'll be fun
54mHow Events Are Reshaping Modern Systems
45mDo Distributed Systems they said. It'll be fun they said.
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets
47mTop 10 Event-Driven Architecture Pitfalls
30mDiving into Event-Driven Architectures (EDA) with Python - Solving complexity at scale