Back to Catalog
Cloud
aws
Saga - Choreography
Coordinate distributed transactions through event-based choreography
Intent & Description
The Saga Choreography pattern coordinates distributed transactions through event-based choreography where each service publishes events after completing local transactions. Other services listen for these events and execute their local transactions accordingly. There is no central coordinator; services communicate through events to maintain eventual consistency.
Real-world Use Case
Use when implementing distributed transactions across microservices without a central coordinator or when you want event-driven coordination.
Source
Advantages
- No single point of failure
- Decentralized coordination
- Natural fit for event-driven architectures
- Flexible and scalable
Disadvantages
- Complex to debug and monitor
- Difficult to understand overall flow
- Requires compensating transactions