Governance of event-driven distributed systems
summary
Argues that event-driven governance must be concrete: a three‑pillar stack of standards, golden paths, tooling; a central event catalog that tracks every producer, consumer and lifecycle; contract testing on external channels and clear internal vs external message boundaries to avoid data inconsistency; pragmatic use of brokers, queues and streaming with attention to polling costs and partition/state limits; SDKs, observability and automation that developers actually use; bounded contexts to isolate change and experimentation environments to validate migrations and scaling before production.
AI-written summary · about
chapters (10)
- 0:00Governance in distributed systems
- 2:13Monolithic struggles and scaling
- 5:50Microservices and event-driven
- 9:05Ownership and observability challenges
- 11:13Governance pillars standards patterns
- 14:45Golden patterns for event-driven
- 16:53Streaming vs request-reply trade-offs
- 18:24Bounded contexts and infrastructure
- 19:28Tooling for engineering teams
- 21:15Conclusion and key takeaways
related talks
51mComplex Event Flows in Distributed Systems
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets
42mDesign Principles for an Event-Driven Architecture
54mHow Events Are Reshaping Modern Systems
47mComplex event flows in distributed systems
42mApplication Architectures: The shadows and highlights of Event Driven Design
38mEvent Design & Event-first Development
46mManaging Event Driven Architectures