saga-orchestration

Coordinate distributed transactions with saga orchestration and reverse-order compensations.

Updated Aug 27, 2026

Search Tags:#microservices #distributed systems #compensation #fault tolerance #workflow recovery #event-driven architecture #saga orchestration

Ready to run

npx skills add https://github.com/schalappe/skills --skill saga-orchestration-schalappe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: saga-orchestration
Source: https://github.com/schalappe/skills/tree/main/saga-orchestration
Command: npx skills add https://github.com/schalappe/skills --skill saga-orchestration-schalappe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves inconsistent system state when a multi-service workflow partially fails by coordinating saga steps and running compensating actions for any completed work.

Core Features & Use Cases

Saga orchestration with compensations: Persist saga state, dispatch each step as a command, and compensate completed steps in reverse order when a later step fails.
Orchestration decision guidance: Choose orchestration vs choreography based on step count, ordering needs, audit trail requirements, and human/durable execution.
Production hardening: Emphasize idempotent steps, correlation IDs, durable replay, timeouts, and handling compensation failures via retry/DLQ/manual intervention.

Quick Start

Ask an AI to design an orchestrated saga for your order fulfillment or payment pipeline that guarantees rollback-like recovery across service boundaries when any step fails.

Frequently Asked Questions about saga-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I handle distributed transaction rollback when a microservices workflow partially fails?▼

Distributed transaction rollback for partially failed microservices workflows is handled by coordinating saga steps and executing compensating actions in reverse order for any completed work, ensuring consistent system state across service boundaries.

What is the difference between saga orchestration and choreography for event-driven architecture?▼

Saga orchestration centrally coordinates step dispatch and compensations, whereas choreography uses event-driven reactions. Orchestration is preferred for complex workflows needing strict ordering, audit trails, durable replay, and human intervention states.

How do I design a saga for order fulfillment and payment pipelines across independently owned services?▼

Design a saga for order fulfillment and payment pipelines by persisting step state, dispatching commands to each service, and running reverse-order compensations for long-running business workflows if any later step fails.

Do I need idempotent step execution for saga orchestration and workflow recovery?▼

Yes, idempotent step execution keyed by saga_id and step_name is required for saga orchestration. It ensures safe replay recovery during workflow recovery when per-step timeouts trigger retries across distributed systems.

What happens when a compensation action fails during a multi-step rollback in a distributed system?▼

When a compensation action fails during a multi-step rollback, the saga orchestration explicitly handles the failure through retry mechanisms, routes the event to a dead letter queue, and enters an operator intervention state.

When should I not use saga orchestration for microservices fault tolerance?▼

You should not use saga orchestration when your distributed workflows lack durable persistence requirements, have very few steps without strict ordering needs, or do not require audit trails and replay recovery for fault tolerance.