Saga pattern for distributed transactions in Microservices - Architecture Diagram

System Overview - Saga pattern for distributed transactions

The Saga pattern manages distributed transactions across multiple microservices without locking resources. It breaks a large transaction into smaller steps, each handled by a service, with compensating actions to undo changes if something fails. This ensures data consistency and reliability in complex systems.

Architecture Diagram

User
  |
  v
API Gateway
  |
  v
Saga Orchestrator
  |       |       |
  v       v       v
Service A  Service B  Service C
  |         |         |
  v         v         v
Database A Database B Database C

Components

User

actor

Initiates the distributed transaction request

API Gateway

gateway

Receives user requests and routes them to the Saga Orchestrator

Saga Orchestrator

orchestrator

Controls the sequence of service calls and manages compensations on failure

Service A

service

Executes first step of the transaction and updates Database A

Service B

service

Executes second step of the transaction and updates Database B

Service C

service

Executes final step of the transaction and updates Database C

Database A

database

Stores data for Service A

Database B

database

Stores data for Service B

Database C

database

Stores data for Service C

Request Flow - 13 Hops

User → API Gateway

API Gateway → Saga Orchestrator

Saga Orchestrator → Service A

Service A → Database A

Service A → Saga Orchestrator

Saga Orchestrator → Service B

Service B → Database B

Service B → Saga Orchestrator

Saga Orchestrator → Service C

Service C → Database C

Service C → Saga Orchestrator

Saga Orchestrator → API Gateway

API Gateway → User

Failure Scenario

Component Fails:Service B

Impact:Step 2 fails, transaction cannot complete; previous step (Service A) changes must be undone

Mitigation:Saga Orchestrator triggers compensating transaction on Service A to rollback step 1 changes, then reports failure to user

Architecture Quiz - 3 Questions

Which component manages the sequence of distributed transaction steps and compensations?

A API Gateway

B Saga Orchestrator

C Service A

D Database B

Design Principle

The Saga pattern breaks a large distributed transaction into smaller steps managed by an orchestrator. Each step updates its own database and confirms success. If any step fails, compensating actions undo previous changes, ensuring eventual consistency without locking resources.

Practice

1. What is the main purpose of the Saga pattern in microservices?

easy

A. To replicate data across multiple databases synchronously

B. To manage distributed transactions by breaking them into smaller steps with compensations

C. To speed up database queries by caching results

D. To lock all resources until the transaction completes

Solution

1. Step 1: Understand distributed transactions challenges

   Distributed transactions across microservices are hard because locking resources is inefficient and can cause delays.

2. Step 2: Identify Saga pattern role

   The Saga pattern breaks a big transaction into smaller steps, each with a compensating action to undo if needed, avoiding locks.

3. Final Answer:

   To manage distributed transactions by breaking them into smaller steps with compensations -> Option B

4. Quick Check:

   Saga pattern = distributed transaction management [OK]

Hint: Saga means small steps with undo actions for transactions [OK]

Common Mistakes:

• Thinking Saga locks resources like traditional transactions
• Confusing Saga with caching or replication
• Assuming Saga runs all steps in parallel

2. Which of the following is the correct sequence in a Saga pattern transaction?

easy

A. Execute steps and compensations simultaneously

B. Run compensations first, then execute all steps

C. Execute only compensations without any steps

D. Execute steps sequentially, then run compensations if any step fails

Solution

1. Step 1: Understand Saga execution flow

   Saga executes each step in order. If a step fails, compensations undo previous steps.

2. Step 2: Confirm correct sequence

   Compensations run only after a failure, never before or simultaneously with steps.

3. Final Answer:

   Execute steps sequentially, then run compensations if any step fails -> Option D

4. Quick Check:

   Steps then compensations = correct Saga flow [OK]

Hint: Steps run first; compensations only if failure occurs [OK]

Common Mistakes:

• Running compensations before any step
• Running steps and compensations at the same time
• Skipping compensations on failure

3. Consider a Saga with three steps: A, B, and C. Step B fails after A succeeds. What happens next?

medium

A. Saga retries step B indefinitely without compensation

B. Step C runs regardless of failure

C. Compensation for step A runs, then Saga aborts

D. No compensation runs; Saga commits partial results

Solution

1. Step 1: Analyze failure impact in Saga

   When step B fails, Saga must undo previous successful steps to keep data consistent.

2. Step 2: Identify compensation actions

   Compensation for step A runs to rollback its changes, then Saga aborts without running step C.

3. Final Answer:

   Compensation for step A runs, then Saga aborts -> Option C

4. Quick Check:

   Failure triggers compensation rollback [OK]

Hint: Failure in middle triggers compensations backward [OK]

Common Mistakes:

• Assuming later steps run after failure
• Thinking Saga retries endlessly without rollback
• Ignoring compensation steps

4. A developer implemented a Saga but noticed data inconsistencies after failures. What is the most likely cause?

medium

A. Compensation actions are missing or incomplete

B. All steps are executed synchronously

C. Steps are too small and independent

D. Saga pattern locks all resources during execution

Solution

1. Step 1: Identify cause of inconsistencies

   Data inconsistencies after failure usually mean rollback (compensation) did not happen properly.

2. Step 2: Check compensation implementation

   If compensation actions are missing or incomplete, previous steps cannot be undone, causing inconsistency.

3. Final Answer:

   Compensation actions are missing or incomplete -> Option A

4. Quick Check:

   Missing compensation = inconsistency [OK]

Hint: Always implement full compensations for each step [OK]

Common Mistakes:

• Assuming synchronous execution causes inconsistency
• Believing small steps cause inconsistency
• Thinking Saga locks resources like traditional transactions

5. You design a payment system using Saga pattern with steps: debit account, reserve inventory, and confirm order. If inventory reservation fails, what should happen?

hard

A. Run compensation to credit back the debited amount and abort order confirmation

B. Ignore failure and proceed to confirm order

C. Retry inventory reservation indefinitely without compensation

D. Lock all services until inventory is reserved

Solution

1. Step 1: Understand Saga compensation in payment flow

   If inventory reservation fails, previous successful steps (debit account) must be undone to avoid inconsistent state.

2. Step 2: Apply compensation and abort

   Compensation credits back the debited amount, and order confirmation is aborted to maintain consistency.

3. Final Answer:

   Run compensation to credit back the debited amount and abort order confirmation -> Option A

4. Quick Check:

   Failure triggers compensation rollback and abort [OK]

Hint: Failure in middle step triggers rollback of prior steps [OK]

Common Mistakes:

• Proceeding despite failure causing inconsistent state
• Retrying endlessly without rollback
• Locking services defeats Saga benefits