Event-Driven Architecture

In this thread

Article

Eventual Consistency Is a Product Decision

Consistency is usually filed under 'backend detail,' but staleness leaks straight into the interface and the business rules. Deciding how stale is acceptable is a product decision — here is how to treat it like one.

Jul 7, 20268 min read

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.

Jul 7, 20267 min read

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.

Jul 7, 20266 min read

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.

Jul 7, 20265 min read

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.

Jul 7, 20266 min read