The Saga Pattern for Distributed Transactions
Learn how to maintain data consistency across microservices without distributed transactions, using the Saga pattern with choreography and orchestration.
The Saga Pattern for Distributed Transactions is a free System Design Basics for Backend Developers lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the System Design Basics for Backend Developers learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
The Distributed Transaction Problem
In a monolith, one database transaction can update everything atomically. In microservices, each service owns its own database, so a single classic transaction across them is impractical.
How do you keep data consistent when an operation spans multiple services?
Why Not Two-Phase Commit?
Two-phase commit (2PC) can coordinate a distributed transaction, but it locks resources across services and blocks if the coordinator fails. It scales poorly and hurts availability — usually the wrong fit for microservices.
Enter the Saga
A Saga breaks a business transaction into a sequence of local transactions, one per service. Each step publishes an event or sends a command to trigger the next.
There is no global lock — consistency is achieved over time.
Compensating Transactions
If a later step fails, the saga cannot roll back like a database. Instead it runs compensating transactions that semantically undo the earlier steps.
- Order placed -> compensate by cancelling order
- Payment charged -> compensate by refunding
An Order Saga
Consider placing an order: reserve inventory, charge payment, schedule shipping. If payment fails, you compensate by releasing the inventory.
steps = ['reserve_inventory', 'charge_payment', 'schedule_shipping']
compensations = ['release_inventory', 'refund_payment', 'cancel_shipping']
done = []
for i, step in enumerate(steps):
ok = step != 'charge_payment'
if not ok:
print('FAILED at', step)
for j in reversed(range(len(done))):
print('compensate:', compensations[j])
break
done.append(step)
print('ok:', step)Choreography
In choreography, there is no central coordinator. Each service listens for events and reacts by doing its work and emitting the next event. It is decentralized and loosely coupled.
OrderCreated -> (Inventory) -> InventoryReserved
InventoryReserved -> (Payment) -> PaymentCharged
PaymentCharged -> (Shipping) -> OrderShippedChoreography Trade-offs
Choreography is simple for short flows but the overall logic is scattered across services. With many steps it becomes hard to understand and risks cyclic event dependencies.
Orchestration
In orchestration, a central orchestrator tells each service what to do and tracks progress. The workflow lives in one place, making complex sagas easier to reason about and monitor.
Orchestrator:
-> Inventory.reserve()
-> Payment.charge()
-> Shipping.schedule()
on failure -> run compensations in reverseIdempotency Is Mandatory
Messages can be delivered more than once, so every saga step and compensation must be idempotent. Use an idempotency key so re-processing the same message has no extra effect.
Eventual Consistency
Sagas give eventual consistency, not immediate. There is a window where the system is partially updated. Design the UI and business rules to tolerate this — for example, an order shown as PENDING until confirmed.
Choosing an Approach
Use choreography for simple flows with few participants, and orchestration when the workflow is complex or needs central visibility. Either way, make steps idempotent and define a compensation for every action.
Quick Check
Test your understanding of the Saga pattern.
Recap
You learned how microservices stay consistent without distributed transactions:
- Sagas chain local transactions with compensations for failures
- Choreography is decentralized; orchestration is centralized
- Steps must be idempotent against duplicate delivery
- The result is eventual consistency, which the design must tolerate
Frequently asked questions
Is the “The Saga Pattern for Distributed Transactions” lesson free?
Yes — the full text of “The Saga Pattern for Distributed Transactions” is free to read here on the web, and the System Design Basics for Backend Developers course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the System Design Basics for Backend Developers course, upgrade to CoddyKit PRO.
What will I learn in “The Saga Pattern for Distributed Transactions”?
Learn how to maintain data consistency across microservices without distributed transactions, using the Saga pattern with choreography and orchestration. You practise System Design Basics for Backend Developers with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start System Design Basics for Backend Developers?
No prior experience is required. System Design Basics for Backend Developers on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “The Saga Pattern for Distributed Transactions” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this System Design Basics for Backend Developers lesson?
Yes. Every System Design Basics for Backend Developers lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Decomposing Monoliths
- Service Discovery & Registry
- Inter-Service Communication Patterns
- The Saga Pattern for Distributed Transactions