Clean Microservices Communications with CQRS and Event Sourcing

on YouTube ↗40m

" summary

Claims that CQRS plus Event Sourcing yields unidirectional communication paths and much simpler service choreography, demonstrated by a Docker demo that actually builds an HTTP command API, an append‑only event store, MongoDB read models, and a change notifier using signal IO for live updates. Commands become persisted events, read models subscribe and emit commands for side effects (exchange rates, order confirmation), replayability and eventual consistency work in practice in the demo.

AI-written summary · about

" chapters (13)

1. 0:00Microservices communication challenges
2. 1:02CQRS and event sourcing overview
3. 3:13Service call chain complexity
4. 8:13Command Query Responsibility Segregation
5. 10:20Event sourcing principles and demo
6. 13:33Live CQRS and event sourcing demo
7. 18:53Read models and event data
8. 21:41Unidirectional CQRS communication
9. 24:14Read model side effects
10. 27:25Command processor handling commands
11. 28:30Eventual consistency in systems
12. 30:17Real-time updates with notifications
13. 34:31Summary and Q&A

" related talks

• 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
• 56mDeveloping Event-driven Microservices w/Event Sourcing and CQRSChris Richardson · Philly ETE 2015
• 01h 25mBuilding microservices with event sourcing and CQRSMichael Ploed · SpringOne2GX 2015
• 55m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Riga Dev Days 2019
• 43mCommander: Better Distributed Applications through CQRS and Event SourcingBobby Calderwood · Strange Loop 2016
• 46mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Voxxed Days Bucharest 2018
• 48mNodeJS Microservices + CQRS + Event Sourcing — Why Do I Do This?Roman Sachenko · JS Fest 2018