DDD, event sourcing and CQRS – theory and practice

on YouTube ↗01h 05m

" summary

Domain language becomes commands and events not CRUD and the system stores a replayable log so past actions answer new analytics questions; implementation uses Vulcan kit, Docker containers, an event store, message queue and separate read/write models so reads scale and accept eventual consistency. The presenter reimplements nevercompletedgame as a JavaScript backend plus React client, hardcodes riddles, reaches about 40 levels in the original puzzle and shows the game running locally with live projections and replay-based queries.

AI-written summary · about

" chapters (14)

1. 0:00Introduction
2. 1:40Never completed game
3. 8:50What your users want
4. 13:07Terminology
5. 18:15Guessing
6. 22:27Domain
7. 28:02CQRS
8. 30:55CQRS Pattern
9. 32:10What is CQRS
10. 33:37How CQRS works
11. 37:17The typical CQRS approach
12. 40:23CQRS eventual consistency
13. 43:46Cap Theorem
14. 51:32Implementation

" related talks

• 30mDomain-Driven Design + Command Query Responsibility Segregation + Event SourcingValerio Del Bello, Massimo Nardelli · Codemotion Rome 2015
• 49mCQRS and Event Sourcing explainedStefan Priebsch · International PHP Conference Spring 2018
• 52mEvent Sourcing and CQRSLutz Huehnken · Scala Days Copenhagen 2017
• 48mNodeJS Microservices + CQRS + Event Sourcing — Why Do I Do This?Roman Sachenko · JS Fest 2018
• 42mCQRS and Event Sourcing with LagomMiel Donkers · Voxxed Days Vienna 2017
• 45mThe Practical Road towards CQRS and Event SourcingSteven van Beelen · Jfokus 2022
• 56mDeveloping Event-driven Microservices w/Event Sourcing and CQRSChris Richardson · Philly ETE 2015
• 43mCommander: Better Distributed Applications through CQRS and Event SourcingBobby Calderwood · Strange Loop 2016