Command Query Responsibility Segregation

on YouTube ↗04m

" summary

Explains that CQRS literally splits command handling from queries so writes use one model and reads another, usually combined with event sourcing that stores immutable events in an event store and rebuilds state by replaying them. Shows an order flow: command → validation → event → event store → message bus → read model → query API. Claims higher read/write performance and easy DB rebuilds but notes added complexity, versioning headaches on replay, and need for a robust message bus.

AI-written summary · about

" chapters (6)

1. 0:00Intro
2. 0:30Main principle
3. 0:54Event sourcing
4. 1:16Types of events
5. 1:53Reduced data view
6. 3:17Pros Cons

" related talks

• 59mCQRS pitfalls and patternsUdi Dahan · NDC Oslo 2023
• 30mDomain-Driven Design + Command Query Responsibility Segregation + Event SourcingValerio Del Bello, Massimo Nardelli · Codemotion Rome 2015
• 51mCQRS + ES = CRUD, QEDValentin Kasas, Damien Gouyette · Scala.IO 2016
• 40mClean Microservices Communications with CQRS and Event SourcingOliver Sturm · Øredev 2024
• 36mCQRS with ErlangBryan Hunter · Strange Loop 2013
• 17m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Voxxed Days Microservices 2019
• 40m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Voxxed Days Cluj-Napoca 2019
• 52mGoing eventually consistent with CQRSManel Sellés · Software Craftsmanship Barcelona 2017