saga-orchestration

You manage distributed transactions across microservices by applying Saga patterns, which coordinate multi-service workflows and execute compensating actions to roll back failed steps like payment or shipment.

In event-driven saga workflows, orchestration uses a central coordinator to drive multi-service execution, whereas choreography relies on services reacting to events independently; both support state management and compensation handling.

You handle compensation in an order processing workflow by defining rollback paths for failed steps, allowing the saga to trigger compensating actions across services like inventory and payment to maintain data consistency.

Yes, you can use saga orchestration for multi-service workflows involving inventory, payment, and shipping, coordinating event-driven execution and state management across these distributed services with clear rollback paths.

You should use a saga pattern instead of a traditional distributed transaction when you need event-driven execution across microservices, especially in long-running workflows where compensating actions are more viable than locking resources.