saga-orchestration

You can manage distributed transactions by implementing the saga pattern, which coordinates multi-step business processes across microservices. This Skill defines saga steps using Python dataclasses and handles cross-aggregate workflows through orchestration or choreography.

Multi-step workflows handle rollback using compensating transactions. If a step fails during a distributed transaction, the saga automatically executes compensating actions to reverse completed steps, maintaining data consistency across microservices.

Orchestration uses a central coordinator to manage multi-step business processes, while choreography relies on event-driven reactions from each service. This Skill supports both patterns for executing distributed transactions and cross-aggregate workflows.

You define saga steps and states using Python dataclasses and abstract base classes. This structure allows you to specify execution logic for multi-step business processes and manage long-running workflows across different services.

Yes, you can automate an order fulfillment process spanning inventory reservation, payment processing, and shipment creation. The saga coordinates these distributed transaction steps and triggers rollback mechanisms if any individual service fails.