Sagas & Distributed Transactions
Studies in this cluster, in series order. Each one keeps its own URL.
Distributed systems
Raft consensus, replication, consistent hashing, saga-style distributed transactions, two-phase commit, and conflict-free replicated data types.
Sagas & Distributed Transactions
6 studies- 1.Sagas & Distributed Transactions — Orchestration, Choreography & CompensationsInterview hub on sagas versus 2PC, orchestration versus choreography, compensations, deadlines, and reconciliation for multi-service business transactions.
- 2.Two-Phase Commit vs Sagas — Why 2PC Breaks at ScaleWhy 2PC blocks at scale, how that compares with sagas, and when a shared-database ACID transaction still wins.
- 3.Orchestration vs Choreography — Central Coordinator vs Event DanceCentral coordinator versus an event dance for sagas, with decision guidance and pointers to outbox, inbox, and deadlines.
- 4.Compensating Transactions — Idempotent Undo & Semantic RollbackIdempotent semantic undo for sagas: reverse-order compensations, void versus refund, and reversing ledger entries.
- 5.Saga State Machines — Timeouts, Retries & DeadlinesSaga state machines with per-step timers, whole-saga deadlines, bounded retries, and durable state.
- 6.Saga Failure Modes — Poison Steps, Partial Failure & ReconciliationPoison steps, partial failure, dead-letter quarantine, and idempotent reconciliation for sagas that miss their SLA.