saga-orchestration

Saga orchestration handles long-running workflows by coordinating multi-step business processes across microservices, executing compensating transactions to undo previous steps and maintain data consistency when failures occur.

Choreography uses event-driven communication where services react independently, while orchestration centrally coordinates the saga steps, defining actions and compensating transactions to ensure resilient distributed transaction management.

Implement compensating transactions by defining rollback actions within your saga pattern, which automatically execute to undo previously completed steps and ensure graceful failure handling when a distributed transaction step fails.

Yes, saga patterns support long-running business processes in microservices by managing extended multi-step workflows, tracking step completion, and executing compensating transactions if failures occur during the distributed transaction lifecycle.

You should avoid the saga pattern when strict ACID consistency is required across all services immediately, because sagas prioritize eventual consistency by relying on compensating transactions rather than distributed locks.