Turning Request-response on its Head
summary
Claims that replacing synchronous retries with events and promises handles unreliable networks and latency, and treats local stores as materialized views fed by event streams. Shows how to split event-processing code from query-serving code to derive CQRS from first principles, cutting retry complexity and making read models explicit. Focuses on architectural pattern and mental model rather than libraries, illustrating the concrete transformation and why it yields clearer separation of concerns.
AI-written summary · about
related talks
44mFrom Synchronous to Asynchronous Distributed Microservices
01h 25mBuilding microservices with event sourcing and CQRS
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
51mPatterns & Practices of Implementing Event-driven MicroSvc...
46mMicroservices Data Patterns: CQRS & Event Sourcing
04mCommand Query Responsibility Segregation
17m7 Reasons why your microservices should use Event Sourcing & CQRS
59mCQRS pitfalls and patterns