/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
Building Scalable and Maintainable Systems with Event Sourcing
Event sourcing can enhance your systems scalability and maintainability. Learn how to implement it effectively with this comprehensive…
2 min read
Unleash the Power of Efficiency with Command-Query Responsibility Segregation (CQRS)
Command-Query Responsibility Segregation (CQRS) is an architectural pattern that separates the responsibilities of writing data (commands)…
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: From Encryption to Observability
Imagine this scenario: a customer exercises their right to erasure. Delete their data, simple as that. Except the event store is immutable…