DDD, event sourcing and CQRS – theory and practice
summary
Compares concrete mechanics: models commands like open game, emits events into an event store, and builds denormalized read model projections fed by a message queue to illustrate eventual consistency and CAP tradeoffs. Implements a JavaScript backend with Vulcan kit, runs locally in Docker, and wires a small React client — the demo is playable and reaches level 13 live; the original puzzle has 40 levels (only 14 completed historically), and the repo plus runnable kit is published.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:40Never completed game
- 8:50What your users want
- 13:07Terminology
- 18:15Guessing
- 22:27Domain
- 28:02CQRS
- 30:55CQRS Pattern
- 32:10What is CQRS
- 33:37How CQRS works
- 37:17The typical CQRS approach
- 40:23CQRS eventual consistency
- 43:46Cap Theorem
- 51:32Implementation
related talks
22mGraphQL and CQRS, a Perfect Fit?
50mAn Introduction to CQRS and Event Sourcing Patterns
26mEvent-Sourcing your React-Flux applications
40mController Control: Designing Domains for Web Applications
44mAll the cool kids...
43mUnraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture
43mEvent driven development
54mThinking in Events