Article
Why Event-Driven Architectures Exist
Direct calls between services are simple until they aren't. Event-driven architecture is the answer to a specific failure of tightly coupled systems — here is the problem it actually solves.
Knowledge domains
Software Architecture
The shapes systems take, and the trade-offs that give them those shapes.
In this domain
Latest resources
Reference
What Is CQRS?
A canonical explanation of CQRS: treating reads and writes as two different problems with two different models, why that split exists, and when it is worth the cost.
Reference
What Is Event Sourcing?
A canonical explanation of event sourcing: storing the full history of what happened as an append-only log of facts, and deriving current state by replaying it.
Reference
What Is the Outbox Pattern?
A canonical explanation of the outbox pattern: how to update a database and publish an event without the two silently drifting apart when one of them fails.