Saga Pattern

The Saga pattern manages data consistency across microservices in distributed transaction scenarios without two-phase commit (2PC). A Saga coordinates a sequence of local transactions, executing compensating transactions backward if any intermediate step fails.

When to Use

• Distributed Transactions Across Microservices: Coordinating multi-step business transactions without two-phase commit (2PC) locks.
• E-Commerce Checkout & Fulfillment: Managing sequences spanning inventory reservation, payment charging, order placement, and delivery dispatch.
• Long-Running Business Processes: Orchestrating processes that span seconds, minutes, or hours with explicit failure compensation.
• Failure Recovery & State Reversal: Rolling back partially completed distributed steps using compensating transactions.

Quick Start