So You Want to Build An Event Driven System?
summary
Covers concrete patterns and tradeoffs for building event driven systems: publish/subscribe via topics or queues, protecting subscribers with a durable queue, choosing between fat vs sparse events and using a consistent metadata/data schema with versioning, enforcing changes via lightweight RFC governance, handling failures with the outbox pattern or change data capture (DynamoDB streams), enriching events via pointers (S3) to avoid callbacks, adding OpenTelemetry traceparent for observability, and using CQRS plus asynchronous commands for scalable queries and eventual consistency.
AI-written summary · about
chapters (17)
- 0:00Event driven systems matter
- 2:32Microservices challenge
- 7:08Defining event driven architecture
- 11:23Event types trade-offs
- 14:11Core components
- 17:19Communication benefits
- 19:04Event storming
- 22:52Governance and schema
- 26:26Fat vs sparse events
- 30:20Asynchronous consistency
- 33:32Integrating non-event systems
- 36:21Observability
- 38:06Boundaries and sync layers
- 41:58Commands events queries
- 44:02Command Query Responsibility Segregation
- 47:14Publishing failures
- 50:22Event driven design
related talks
54mSo You Want to Build An Event Driven System?
52mSo You Want to Build An Event Driven System?
48mEvent-Driven Architecture – Benefits and Pitfalls
27mPatterns for Event-Driven APIs
31mDemystifying Event-Driven Architectures
41mGetting started with Event-Driven Architectures in 2023
49mSo You Want to Maintain a Reliable Event-Driven System
39mBuilding next-gen applications with event-driven architecture