Commander: Better Distributed Applications through CQRS and Event Sourcing
summary
Claims a concrete pattern and a working implementation: writes commands to Kafka, uses Kafka Streams for reactive processors, and Clojure in the HTTP layer with Datomic for persistence. The system records immutable commands (HTTP 202 async, optional sync true), business logic consumes commands and emits events, read-optimized views are built by micro-consumers, and the demo runs under load at scale for high transaction volumes and organization-wide auditing and analytics.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:38Bobbys background
- 6:10Architecture
- 8:49Event Sourcing
- 9:51Data Loss by Design
- 11:53Data Models
- 13:13Rest
- 14:19Conways Law
- 16:44Command Architecture
- 20:14Event Architecture
- 21:27Secure Eyes
- 22:46Primary Service Team
- 25:52Command A Component
- 29:12Demo
- 34:06Summary
- 37:15Announcement
related talks
44mFrom REST to CQRS with Clojure, Kafka, & Datomic
40mClean Microservices Communications with CQRS and Event Sourcing
43mKey-Value, Event-Sourcing, Cqrs, Pub/Sub as a Service, Java, Javascript
46mMicroservices Data Patterns: CQRS & Event Sourcing
30mDomain-Driven Design + Command Query Responsibility Segregation + Event Sourcing
01h 25mBuilding microservices with event sourcing and CQRS
51mMicroservices Data Patterns: CQRS & Event Sourcing
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
