Empowering Architectural Evolution: Governing Event-Driven Solutions
summary
Argues that governing event-driven systems requires a metadata-first approach: a centralized metadata catalog with quality phases (raw → documented → curated), a producer validation gateway to reject malformed events, and language client libraries that enforce schema and naming conventions. Recommends schema evolution tactics (default values, avoid enums, N‑minus‑2 or Stripe‑style pinning with downcasting), a metadata dictionary to prevent sprawl, CloudEvents-style headers for schema links, and an observable event store for auditing, analytics and access control.
AI-written summary · about
chapters (15)
- 0:00Event-driven governance intro
- 3:00Why governance matters
- 7:14Balancing agility and risk
- 10:03Governance layers
- 13:35Metadata catalog foundation
- 20:15Evolving metadata quality
- 23:46Schema evolution rules
- 30:31Preventing metadata sprawl
- 32:57Event structuring standards
- 37:08Producer-side validation
- 39:37Event discovery tips
- 41:43Event visualization tools
- 42:46Access control and validation
- 45:33Governance with observability
- 46:55Key takeaways
related talks
01h 13mChange Is Inevitable: Versioning Event-Driven Systems
55mNavigating complexity in event-driven architectures: A domain-driven approach
44mComplexity is the Gotcha of Event-driven Architecture
42mDesign Principles for an Event-Driven Architecture
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets
26mMetamorphosis: Microservices & Event-driven Architecture
52mNavigating complexity in event-driven architectures: A domain-driven approach
37mBuilding Event-driven Apps at Scale