# Saga - Orchestration

> Coordinate distributed transactions through a central orchestrator

- **Category**: Cloud
- **Subcategory**: aws
- **Canonical URL**: https://designpattern.fyi/patterns/aws_saga_orchestration/

---

## Description
The Saga Orchestration pattern coordinates distributed transactions through a central orchestrator that manages the overall transaction flow. The orchestrator tells each service which local transaction to execute in which order. If a step fails, the orchestrator executes compensating transactions to undo previous steps, ensuring data consistency across services.


## Use Cases
Use when implementing distributed transactions that require centralized coordination or when you need better visibility and control over the transaction flow.





## Trade-offs


### Advantages

- Centralized control and visibility

- Easier to understand and monitor

- Explicit transaction flow definition

- Better error handling and recovery




### Considerations & Drawbacks

- Single point of failure (the orchestrator)

- Can become complex with many services

- Requires orchestrator infrastructure







---
**Reference**: [Original Source](https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/saga-orchestration.html)