Why Saga pattern for distributed transactions in HLD? - Purpose & Use Cases

The Big Idea

What if your complex multi-step process could fix itself automatically when something goes wrong?

The Scenario

Imagine you are coordinating a group of friends to buy different items for a party. Each friend must buy their item and confirm it. If one friend fails, you have to call everyone back to cancel or fix their purchases manually.

The Problem

Doing this by calling each friend one by one is slow and confusing. If someone forgets to cancel or confirm, the whole plan breaks. It's easy to lose track and end up with missing or extra items.

The Solution

The Saga pattern breaks the big task into smaller steps with clear success and failure actions. If one step fails, it automatically triggers compensations to undo previous steps, keeping everything consistent without manual calls.

Before vs After

✗ Before

try {
  step1();
  step2();
  step3();
} catch (error) {
  undoStep2();
  undoStep1();
}

✓ After

startSaga()
  .then(step1)
  .then(step2)
  .then(step3)
  .catch(compensatePreviousSteps)

What It Enables

It enables reliable, automatic handling of complex multi-step processes across different systems without losing data or consistency.

Real Life Example

When booking a trip online, the Saga pattern ensures your flight, hotel, and car rental bookings all succeed or all get canceled properly if one fails.

Key Takeaways

Manual coordination of distributed tasks is slow and error-prone.

Saga pattern manages each step with clear success and rollback actions.

This keeps distributed systems consistent and reliable automatically.