Sagas: transactions without a shared rollback
Why two-phase commit fails across microservices, how a saga replaces it with local transactions and compensations, choreography versus orchestration, the pivot and forward recovery, a crash-safe orchestrator with idempotency keys, booking and trip sagas, the mistakes that leave sagas stuck, and how to run them in production.
01 · Previously
W05 · DAY 02 · Distributed Transactions — The Saga Pattern
From one read to a whole transaction.
Previously: consistency models
Previously, on Day 1, you learned exactly who sees a write, and when: linearizable down to eventual, CAP during partitions, and strong consistency where it matters, like reserving inventory.
0:00 / 19:45