7 Reasons why your microservices should use Event Sourcing & CQRS

on YouTube ↗17m

" summary

Advocates using Event Sourcing + CQRS to store state as an insert‑only event log and maintain a separate read model that can be rebuilt by replaying events, claiming this handles spikes by making writes fast and reads eventually consistent. Calls out Kafka and the pull consumer pattern, and details messaging semantics (at‑most‑once, at‑least‑once, exactly‑once) and producer retry complexity. Argues the pattern reduces coupling between services, simplifies reliable pipelines, and raises the concurrency ceiling compared with CRUD on a single DB.

AI-written summary · about

" chapters (12)

1. 0:00Intro
2. 0:23What is Event Sourcing
3. 0:34What is CQRS
4. 2:19Smooth transition from design
5. 3:51Reduce coupling
6. 6:43ReadWrite performance bottleneck
7. 9:07Concurrency barrier
8. 11:15Simplifying messaging
9. 14:52Pull pattern
10. 15:21Culture shock
11. 15:39Governance
12. 16:27Openminded

" related talks

• 40m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Voxxed Days Cluj-Napoca 2019
• 55m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Riga Dev Days 2019
• 46mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Voxxed Days Bucharest 2018
• 51mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Devoxx Belgium 2017
• 01h 25mBuilding microservices with event sourcing and CQRSMichael Ploed · SpringOne2GX 2015
• 56mDeveloping Event-driven Microservices w/Event Sourcing and CQRSChris Richardson · Philly ETE 2015
• 47mFrom C to Q, One Event at a Time: Event Sourcing in PicturesLorenzo Nicora · Voxxed Days Ticino 2017
• 48mNodeJS Microservices + CQRS + Event Sourcing — Why Do I Do This?Roman Sachenko · JS Fest 2018