An Introduction to CQRS and Event Sourcing Patterns
summary
Clear, runnable C# example shows a CQRS write model that stores events in an Event Store and read-side projections built into RavenDB, with replayable event stream replay to rebuild aggregates and two projections (ward list and age-range demographics). Code uses optimistic concurrency via version numbers, per-projection checkpointing, and a projection manager that can run independently to illustrate eventual consistency. Demo runs a few hundred-line implementation and replays thousands of events to rebuild views.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:20Why this talk
- 2:35Agenda
- 3:24What is an encounter
- 4:07Events
- 7:40DomainDriven Design
- 8:19Auditing Tables
- 10:17Replaying Events
- 12:07CQRS
- 17:44CQRS Architecture
- 23:41Eventually Consistency
- 25:34Demo
- 26:22Solution Overview
- 27:19Commands
- 28:09Handlers
- 29:09Discharge
- 29:51Aggregate Root
- 35:40Projection Manager
- 36:07Handling Events
- 37:15Projections
- 37:53Web Application
- 45:09Web API
- 46:21Monitoring Tools
- 48:41Further Resources
related talks
43mUnraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture
54mThinking in Events
01h 05mDDD, event sourcing and CQRS – theory and practice
26mEvent-Sourcing your React-Flux applications
51mThings I Wish I knew Before I Started with Event Sourcing
43mModern Application Architecture with Scala in Real Life
43mEvent driven development
22mGraphQL and CQRS, a Perfect Fit?