saga-orchestration

To coordinate distributed transactions across microservices, you can use saga patterns that manage long-running business workflows with compensating actions for partial failure recovery. This Skill provides Python-based templates for both orchestrated and choreographed approaches.

In event-driven sagas, orchestration uses a central coordinator to command each service step, while choreography relies on services reacting to events independently. This Skill provides templates and guidance for implementing both coordination styles across your microservices.

Compensation and rollback for failed multi-service workflows are handled by defining specific compensating actions for each saga step. If a service operation fails, the saga pattern triggers these actions to reverse prior steps and maintain data consistency across domains.

Yes, saga patterns are well-suited for long-running business processes like order fulfillment and payments. This Skill provides ready-to-adapt code examples for orchestrating these multi-step workflows across distributed services with reliable failure handling.

The best way to start implementing an orchestrated saga in Python is to instantiate a SagaOrchestrator for your domain, define the transaction steps, and call start with your domain data to begin the workflow across the participating microservices.

You should not use the saga pattern for distributed transactions when strict real-time ACID consistency is required across all services, as sagas prioritize eventual consistency through compensating actions for long-running workflows rather than immediate distributed locks.