Level 3: Distributed systems · L3.4 Sagas, outbox, CQRS & event sourcing
Sagas: transactions across services
Design a saga with compensations, orchestrated vs choreographed.
13 min · Pro
What you take away
- A saga is a sequence of local transactions, each with a compensating action if a later step fails.
And 3 more inside the class, in Pro.
How the class is laid out
- The problem
- The simple version
- The shape, with a failure
- The part people miss: no isolation
- Check your understanding