Going eventually consistent with CQRS
summary
Examines CQRS (separating write and read models) and its benefits, questioning when that separation makes sense. Covers patterns for integrating with external systems in a decoupled way, using eventual consistency, and shows how these ideas are applied in a real project.
AI-written summary · about
chapters (13)
- 0:00Project introduction
- 2:12Monolith problems
- 8:35Initial modeling frustrations
- 12:16Rethinking delivery model
- 16:35Final CQRS solution
- 21:29CQRS key concepts
- 28:59Command and event flow
- 31:51Async projections
- 38:02PHP implementation
- 38:44External scheduler integration
- 41:12Error handling and consistency
- 46:10CQRS benefits
- 49:24Eventual consistency
related talks
59mCQRS pitfalls and patterns
04mCommand Query Responsibility Segregation
30mDomain-Driven Design + Command Query Responsibility Segregation + Event Sourcing
47mFrom C to Q, One Event at a Time: Event Sourcing in Pictures
46mMicroservices Data Patterns: CQRS & Event Sourcing
17m7 Reasons why your microservices should use Event Sourcing & CQRS
30mEventSourcing and CQRS — The Introduction That Was Missing
36mCQRS with Erlang