Change Is Inevitable: Versioning Event-Driven Systems
summary
Explains concrete rules and tooling for evolving event contracts: use schemas (Avro example) and a schema registry to enforce forward/backward/full/transitive compatibility, prefer granular business events while publishing a single public summary, and treat metadata changes as breaking so you create new event types. Gives an Azure Service Bus upgrade recipe (dual publish, subscribe to new topic before unsubscribing old, deduplicate by logical ID) and endorses cloud events and the CNCF X-Registry for discovery and deprecation notifications.
AI-written summary · about
chapters (19)
- 0:00Introduction to challenges
- 2:04Change in distributed systems
- 2:57Event design pitfalls
- 9:26Consumer impact of changes
- 11:09Designing better events
- 14:13Public vs private events
- 22:22Payload format coupling
- 24:41Schemas as contracts
- 27:25Forward compatibility in action
- 30:47Backward compatibility in action
- 34:21Advanced compatibility modes
- 36:54Schema vs semantic versioning
- 40:03Metadata and CloudEvents
- 41:22Managing metadata changes
- 45:36Breaking change strategies
- 47:18Enforcing contracts
- 51:53Introduction to xRegistry
- 59:00Final recap and summary
- 1:03:00Q&A and closing remarks
related talks
48mEmpowering Architectural Evolution: Governing Event-Driven Solutions
55mSo You Want to Maintain a Reliable Event Driven System
52mSo You Want to Build An Event Driven System?
49mSo You Want to Maintain a Reliable Event-Driven System
44mComplexity is the Gotcha of Event-driven Architecture
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets
38mEvent Design & Event-first Development
01h 08mEvent Driven Architecture – Enabling Microservices