saga-orchestration

1# Saga Orchestration
2 
3Patterns for managing distributed transactions and long-running business processes without two-phase commit.
4 
5## Inputs and Outputs
6 
7**What you provide:**
8- Service boundaries and ownership (which service owns which step)
9- Transaction requirements (which steps must be atomic, which can be eventual)
10- Failure modes for each step (transient vs. permanent, retry policy)
11- SLA requirements per step (informs timeout configuration)
12- Existing event/messaging infrastructure (Kafka, RabbitMQ, SQS, etc.)
13 
14**What this skill produces:**
15- Saga definition with ordered steps, action commands, and compensation commands
16- Orchestrator or choreography implementation for your chosen pattern
17- Compensation logic for each participant service (idempotent, always-succeeds)
18- Step timeout configuration with per-step deadlines
19- Monitoring setup: state machine metrics, stuck saga detection, DLQ recovery
20 
21---
22 
23## When to Use This Skill
24 
25- Coordinating multi-service transactions without distributed locks
26- Implementing compensating transactions for partial failures
27- Managing long-running business workflows (minutes to hours)
28- Handling failures in distributed systems where atomicity is required
29- Building order fulfillment, approval, or booking processes
30- Replacing fragile two-phase commit with async compensation
31 
32---
33 
34## Detailed section: Core Concepts
35 
36Moved to `references/details.md`.
37 
38## Detailed section: Templates
39 
40Moved to `references/details.md`.
41 
42## Best Practices
43…