Saga Orchestration & Compensations

Step through multi-service transactions without blocking Two-Phase Commit (2PC). Observe forward execution and automated backward compensating rollbacks.

Saga Execution Pipeline

Inject Failure Point:

1. Create Order

PENDING

Forward: Insert order (status: PENDING)

Compensate: Update order (status: CANCELLED)

2. Reserve Stock

PENDING

Forward: Decrement item stock by 1

Compensate: Increment item stock by 1 (Release)

3. Charge Payment

PENDING

Forward: Authorize Stripe credit card

Compensate: Issue Stripe refund

4. Dispatch Courier

PENDING

Forward: Create FedEx tracking waybill

Compensate: Void FedEx shipping label

Why Sagas Beat 2-Phase Commit (2PC)

2PC requires holding global database row locks until all participants vote commit. If one network partition occurs, the entire system freezes.

Sagas commit each local transaction immediately in its private database. If failure strikes, reverse compensating actions restore eventual consistency with zero blocking locks.

[INIT] Saga Orchestrator FSM ready.

[CONFIG] Select failure point and click "Execute Distributed Saga".

Loading MICROSERVICES::VIZ...