Saga pattern for distributed transactions in HLD - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the first step in a saga transaction.

HLD

def saga_step_1():
    # Start transaction
    [1]

Drag options to blanks, or click blank then click option'

Abegin_transaction()

Bcommit_transaction()

Crollback_transaction()

Dend_transaction()

Attempts:

3 left

💡 Hint

Common Mistakes

Using commit_transaction() before starting the transaction.

Calling rollback_transaction() as the first step.

The first step in a saga transaction is to begin the transaction to ensure all steps are tracked.

2fill in blank

medium

Complete the code to define the compensation action in a saga step.

HLD

def compensate_step():
    # Undo previous action
    [1]

Drag options to blanks, or click blank then click option'

Acommit_transaction()

Bexecute_compensation()

Crollback_compensation()

Dstart_compensation()

Attempts:

3 left

💡 Hint

Common Mistakes

Using commit_transaction() instead of compensation.

Calling rollback_compensation() which is not a standard term.

Compensation in saga means executing a specific action to undo the previous step.

3fill in blank

hard

Fix the error in the saga coordinator logic to handle step failure.

HLD

def saga_coordinator():
    try:
        execute_step_1()
        execute_step_2()
    except Exception:
        [1]  # Handle failure

Drag options to blanks, or click blank then click option'

Aexecute_compensation()

Bcommit_transaction()

Cstart_transaction()

Dignore_error()

Attempts:

3 left

💡 Hint

Common Mistakes

Committing the transaction on failure.

Ignoring the error without compensation.

When a step fails, the saga coordinator must execute compensation to undo previous steps.

4fill in blank

hard

Fill both blanks to correctly define a saga step with its compensation.

HLD

def saga_step():
    try:
        [1]  # Perform action
    except Exception:
        [2]  # Perform compensation

Drag options to blanks, or click blank then click option'

Aexecute_action()

Bexecute_compensation()

Ccommit_transaction()

Dstart_transaction()

Attempts:

3 left

💡 Hint

Common Mistakes

Using commit_transaction() instead of compensation.

Starting a transaction inside the step incorrectly.

The saga step performs an action and if it fails, it executes compensation to undo.

5fill in blank

hard

Fill all three blanks to define a saga coordinator managing steps and compensation.

HLD

def saga_coordinator():
    [1]  # Start saga
    try:
        [2]  # Execute saga steps
    except Exception:
        [3]  # Execute compensation

Drag options to blanks, or click blank then click option'

Astart_transaction()

Bexecute_all_steps()

Cexecute_compensation()

Dcommit_transaction()

Attempts:

3 left

💡 Hint

Common Mistakes

Committing before executing all steps.

Not starting the transaction before steps.

The coordinator starts the saga, executes all steps, and compensates on failure.

Practice

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

easy

A. To replicate data across multiple servers for backup

B. To lock all resources until the transaction completes

C. To speed up database queries by caching results

D. To manage long transactions by splitting them into smaller steps with compensations

Solution

1. Step 1: Understand the problem Saga solves

   The Saga pattern handles distributed transactions by breaking them into smaller steps that can be undone if needed.

2. Step 2: Compare options with Saga's goal

   Locking resources or caching are unrelated to Saga's main goal of managing distributed transactions with compensations.

3. Final Answer:

   To manage long transactions by splitting them into smaller steps with compensations -> Option D

4. Quick Check:

   Saga pattern purpose = Manage transactions with compensations [OK]

Hint: Saga splits big tasks into steps with undo actions [OK]

Common Mistakes:

• Thinking Saga locks resources like traditional transactions
• Confusing Saga with caching or replication techniques
• Assuming Saga only works with single database systems

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

easy

A. Execute steps sequentially, running compensations for previous steps if any step fails

B. Run compensations first, then execute all steps

C. Execute steps and compensations simultaneously

D. Execute steps without any compensations

Solution

1. Step 1: Recall Saga transaction flow

   Saga executes steps one by one. If a step fails, compensations undo previous steps.

2. Step 2: Eliminate incorrect sequences

   Running compensations before steps or simultaneously is incorrect. Skipping compensations breaks consistency.

3. Final Answer:

   Execute steps sequentially, running compensations for previous steps if any step fails -> Option A

4. Quick Check:

   Saga sequence = Steps then compensations on failure [OK]

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

Common Mistakes:

• Running compensations before any step executes
• Assuming compensations run regardless of success
• Thinking steps and compensations run at the same time

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

medium

A. Compensate step A, then abort the Saga

B. Retry step B indefinitely

C. Proceed to step C despite failure

D. Ignore failure and commit all steps

Solution

1. Step 1: Identify failure handling in Saga

   If step B fails, Saga triggers compensations for all previous successful steps, here step A.

2. Step 2: Understand why other options fail

   Retrying indefinitely can cause blocking; proceeding ignores failure; ignoring failure breaks consistency.

3. Final Answer:

   Compensate step A, then abort the Saga -> Option A

4. Quick Check:

   Failure in step B triggers compensation of A [OK]

Hint: Failure triggers undo of prior successful steps [OK]

Common Mistakes:

• Assuming Saga retries failed steps endlessly
• Skipping compensations and continuing steps
• Ignoring failure and committing partial results

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

medium

A. Saga uses asynchronous messaging

B. Compensation actions are missing or incomplete

C. Steps are idempotent and retry safe

D. All steps are executed sequentially

Solution

1. Step 1: Analyze cause of inconsistencies

   Missing or incomplete compensation means failed steps do not undo prior changes, causing inconsistency.

2. Step 2: Evaluate other options

   Sequential execution, idempotency, and async messaging are good practices and do not cause inconsistencies alone.

3. Final Answer:

   Compensation actions are missing or incomplete -> Option B

4. Quick Check:

   Missing compensations cause inconsistencies [OK]

Hint: Check if compensations are properly implemented [OK]

Common Mistakes:

• Blaming sequential execution for inconsistency
• Ignoring importance of compensation actions
• Assuming async messaging causes inconsistency

5. You design a Saga for an e-commerce order process with payment, inventory, and shipping services. Which approach best ensures data consistency across these services?

hard

A. Use a global database lock across all services during the order process

B. Allow each service to commit independently without rollback

C. Implement compensating transactions for each service step to rollback on failure

D. Retry failed steps indefinitely without compensation

Solution

1. Step 1: Understand distributed transaction challenges

   Locking globally is impractical; independent commits without rollback cause inconsistency.

2. Step 2: Apply Saga pattern best practice

   Compensating transactions allow rollback of previous steps if any step fails, ensuring consistency.

3. Final Answer:

   Implement compensating transactions for each service step to rollback on failure -> Option C

4. Quick Check:

   Compensations ensure consistency in distributed Saga [OK]

Hint: Use compensations, not global locks, for distributed consistency [OK]

Common Mistakes:

• Trying to lock all services globally
• Ignoring rollback on failure
• Relying on infinite retries without undo