/blog / series/event-sourcing-cqrs-series
$ Event Sourcing & CQRS in Practice
4 posts, in reading order
Event Sourcing and CQRS as they behave in production: building scalable systems on an append-only event log, keeping read and write models honest, and what happens when the event store itself becomes the bottleneck.
One post goes deep on securing event-sourced financial systems — encryption, key rotation and observability for data that can never be deleted — drawing on years of fintech work where these patterns carry real money.
$ Posts in this series
3 min read
Event Sourcing: State as a History of Events
Storing every change as an event instead of overwriting state: how the history is replayed, where event sourcing fits, and the practices it demands.
2 min read
CQRS: Separating the Write Model from the Read Model
Part 2 of an event sourcing series: splitting commands from queries, what that fixes as data grows, and what it costs to run two models instead of one.
9 min read
Why Your Event Store Becomes a Bottleneck (And How NestJS Microservices Can Fix It)
Your event store processes 10K events/min smoothly, then Black Friday hits. How to scale with distributed NestJS microservices.
20 min read
Securing Event-Sourced Financial Systems
Part 4 of an event sourcing series: PII kept out of events, crypto-shredding for GDPR erasure, locked-down CQRS projections, and auditable observability.