Saga - Orchestration
?
- One of two patterns that handle sequential async requests to various services.
- A single service handles requests/responses to/from various services
- Suitable when
- Need stateful control over multiple services
- Owning saga participants
- Cons
- Orchestrator is a single-point of failure
- Participants do not need awareness of other participants
- Use Cases
- Easy management of code
- When a centralized service is needed
<!--SR:!2025-10-25,1,130-->