State or events? Which shall I keep?
summary
Live-codes two parallel implementations — classic ORM and an event-sourced model — and demonstrates a working Docker Compose example that wires Apache Kafka as the immutable event store. Builds user, friend and aggregate services plus an API gateway; aggregate service materializes read-models (Neo4j/RocksDB examples) to avoid expensive distributed joins. Shows replay/time-travel, audit trail, eventual consistency tradeoffs, suggested GDPR approach (encrypt events or store IDs plus external data), and supplies the GitHub repo with runnable reference architecture.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:47Event sourcing origins
- 8:10Metaphors in design
- 11:01Apache Kafka logs
- 18:51Event sourcing in microservices
- 25:16CQRS and materialized views
- 33:03Reference architecture
- 41:19Q&A
related talks
56mEvents on the outside, on the inside and at the core
43mKey-Value, Event-Sourcing, Cqrs, Pub/Sub as a Service, Java, Javascript
46mEvent-based Architecture & Implementations with Kafka & Atom
01h 13mRefactoring to a System of Systems
44mBuilding event-driven microservices with Scala and Functional Domain Models
58mGame of Streams
51mImmutable data stores and CORS for safety, flexibility and profit
01h 08mEvent Driven Architecture – Enabling Microservices