So You Want to Build An Event Driven System?
summary
A practical guide to turning a microservice order flow into an event driven system using concrete patterns: model business facts as order confirmed event or richer carriage events, use a durable queue between bus and consumer, apply the CloudEvents spec with versioning plus RFC governance for breaking changes, add a small proxy for third‑party loyalty APIs, and protect delivery with a transactional outbox or CDC. Advice includes using OpenTelemetry trace IDs, accepting eventual consistency, starting small on one integration, and the pizza example proves the approach works with these tradeoffs.
AI-written summary · about
chapters (21)
- 0:00The power of stories
- 2:59Tackling coupling
- 6:30Why event-driven?
- 8:43Event theory
- 11:53Event-first design
- 15:15Fat vs thin events
- 17:08Publish-subscribe patterns
- 20:24Implementing event-driven
- 22:30Event storming
- 24:28Governance and schema
- 26:34Cloud events specification
- 29:03Applying Pell's law
- 30:24Integration patterns
- 33:32Eventual consistency
- 35:49Asynchronous commands
- 38:53Legacy integration
- 40:49Observability and tracing
- 42:25System boundaries
- 44:27CQRS pattern
- 47:05Transactional outbox
- 49:25Conclusion and advice
related talks
54mSo You Want to Build An Event Driven System?
52mSo You Want to Build An Event Driven System?
49mSo You Want to Maintain a Reliable Event-Driven System
51mComplex Event Flows in Distributed Systems
58mImplementing Event-driven Microservices
44mUnlocking Business Agility with Event-Driven Architectures
47mEvent-Driven Microservices = Microservices Done Right
57mEvent Driven Collaboration