Back to Catalog
Cloud
azure
Choreography
Let individual services decide when and how business operations are processed
Intent & Description
The Choreography pattern lets individual services decide when and how a business operation is processed, instead of depending on a central orchestrator. Services communicate through events and each service reacts to events autonomously. This provides decentralization and flexibility but can be harder to coordinate.
Real-world Use Case
Use when you want decentralized coordination between services or when the workflow is simple enough that individual services can make autonomous decisions.
Source
Advantages
- No single point of failure
- Decentralized control
- Flexible and adaptable
- Natural fit for event-driven architectures
Disadvantages
- Complex to understand overall flow
- Difficult to debug and monitor
- Requires compensating transactions