Goodbye history tables, hello full audit- exploring message streams & event sourcing
summary
Argues that replacing history tables with message streams yields full audit and replayable state, demonstrated with a local Kafka + Event Store demo, Azure Cosmos DB projections and a consumer/projector pattern that produces current state and a separate history projector for every message. Shows a registration flow that publishes a user registration requested event, subsequent success/failure events, email confirmation and a five‑attempt lockout that actually triggers, and ties logs to messages via activity and causation IDs, proving the approach works end‑to‑end.
AI-written summary · about
chapters (7)
- 0:00Start
- 7:39(a few) Microservices Architecture Goals
- 13:42Important Supporting Concepts
- 16:53Identifying Business Domains
- 21:06Single Responsibility Pattern
- 23:48Identity Management Domain
- 28:45Command Query Responsibility Segregation (CORS)
related talks
52mEvent Sourcing for the Cloud Developer
43mUnraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture
52mEvent Sourcing – the what, why & how
30mEvent Streaming and the Future of Applications
55mMessage Brokers and Containers - the new ESB is “no ESB”
44mEvent Sourcing - You are doing it wrong
48mNodeJS Microservices + CQRS + Event Sourcing — Why Do I Do This?
37mBeyond Microservices: Streams, State & Scalability