Bird
Raised Fist0
Microservicessystem_design~5 mins

Two-phase commit (and why to avoid it) in Microservices - Cheat Sheet & Quick Revision

Choose your learning style10 modes available
LearnWhyDeepArchPracticeChallengeDesignRecallScale

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Recall & Review
beginner
What is the Two-phase commit protocol?
Two-phase commit is a method used to ensure all parts of a distributed system agree to commit a transaction or all abort, maintaining data consistency.
Click to reveal answer
beginner
What are the two phases in the Two-phase commit protocol?
Phase 1: Prepare phase where all participants vote to commit or abort. Phase 2: Commit phase where the coordinator tells all participants to commit or abort based on votes.
Click to reveal answer
intermediate
Why is Two-phase commit considered a blocking protocol?
Because if the coordinator crashes after participants vote to commit but before sending the final decision, participants wait indefinitely, blocking resources.
Click to reveal answer
intermediate
Name one major drawback of using Two-phase commit in microservices.
It reduces system availability and scalability because services must lock resources and wait for the coordinator, causing delays and potential deadlocks.
Click to reveal answer
intermediate
What are some alternatives to Two-phase commit in microservices?
Alternatives include eventual consistency patterns like Saga, event-driven architectures, and compensating transactions to avoid blocking and improve scalability.
Click to reveal answer
What does the coordinator do in the first phase of Two-phase commit?
AAsks participants if they can commit
BCommits the transaction immediately
CAborts the transaction
DSends the final commit decision
Why can Two-phase commit cause system blocking?
ABecause it commits transactions too fast
BBecause participants wait for the coordinator's final decision
CBecause it does not use locks
DBecause it only works on a single machine
Which of the following is NOT a reason to avoid Two-phase commit in microservices?
AIt improves scalability
BIt reduces availability
CIt can cause deadlocks
DIt increases latency
What is a common alternative to Two-phase commit for distributed transactions?
ANo transaction management
BSingle-phase commit
CManual commit
DSaga pattern
In Two-phase commit, what happens if a participant votes to abort during the prepare phase?
AThe coordinator ignores the vote
BThe transaction commits anyway
CThe coordinator tells all to abort
DThe participant retries automatically
Explain the Two-phase commit protocol and why it can cause problems in microservices.
Think about how waiting for a coordinator affects distributed services.
You got /4 concepts.
    Describe alternatives to Two-phase commit and how they improve distributed transaction handling in microservices.
    Consider patterns that avoid locking and blocking.
    You got /4 concepts.

      Practice

      (1/5)
      1. What is the main purpose of the two-phase commit protocol in microservices?
      easy
      A. To automatically retry failed requests
      B. To speed up communication between services
      C. To allow services to work independently without coordination
      D. To ensure all services agree on a transaction before committing

      Solution

      1. Step 1: Understand the role of two-phase commit

        Two-phase commit is designed to make sure all parts of a distributed transaction agree to commit or abort together.

      2. Step 2: Identify the main goal in microservices

        Its main goal is to keep data consistent across multiple services by coordinating their commit decisions.

      3. Final Answer:

        To ensure all services agree on a transaction before committing -> Option D

      4. Quick Check:

        Two-phase commit = agreement before commit [OK]
      Hint: Two-phase commit means all must say yes before commit [OK]
      Common Mistakes:
      • Thinking it speeds up communication
      • Believing services act independently
      • Assuming it retries failed requests automatically
      2. Which of the following correctly describes the two phases in the two-phase commit protocol?
      easy
      A. Abort phase where coordinator asks, Prepare phase where services finalize
      B. Prepare phase where coordinator asks, Commit phase where services finalize
      C. Commit phase where coordinator asks, Prepare phase where services finalize
      D. Prepare phase where services finalize, Commit phase where coordinator asks

      Solution

      1. Step 1: Recall the two phases names and order

        The first phase is the prepare phase where the coordinator asks all services if they can commit.

      2. Step 2: Understand the commit phase

        If all agree, the coordinator sends a commit command to finalize the transaction.

      3. Final Answer:

        Prepare phase where coordinator asks, Commit phase where services finalize -> Option B

      4. Quick Check:

        Prepare then commit = correct phase order [OK]
      Hint: Prepare asks, commit finalizes transaction [OK]
      Common Mistakes:
      • Mixing up the order of prepare and commit phases
      • Confusing abort with prepare phase
      • Thinking services finalize before coordinator asks
      3. Consider a microservices system using two-phase commit. If one service fails to respond during the prepare phase, what is the expected outcome?
      medium
      A. The coordinator ignores the failure and proceeds
      B. The coordinator commits the transaction anyway
      C. The coordinator aborts the transaction and tells all services to rollback
      D. The coordinator retries the prepare phase indefinitely

      Solution

      1. Step 1: Analyze failure during prepare phase

        If any service fails to respond or votes no during prepare, the coordinator must abort to keep consistency.

      2. Step 2: Understand coordinator's action

        The coordinator sends abort commands to all services to rollback any partial changes.

      3. Final Answer:

        The coordinator aborts the transaction and tells all services to rollback -> Option C

      4. Quick Check:

        Failure in prepare = abort transaction [OK]
      Hint: Any no or failure in prepare means abort [OK]
      Common Mistakes:
      • Assuming commit happens despite failure
      • Thinking coordinator retries forever
      • Ignoring failure and proceeding anyway
      4. A developer notices that their two-phase commit implementation causes long delays and system hangs when a service crashes. What is the most likely cause?
      medium
      A. The coordinator is waiting indefinitely for responses from crashed services
      B. The services are committing too quickly without coordination
      C. The coordinator is skipping the prepare phase
      D. The services are not logging their transactions

      Solution

      1. Step 1: Identify cause of delays and hangs

        In two-phase commit, the coordinator waits for all services to respond during prepare phase.

      2. Step 2: Understand impact of crashed services

        If a service crashes, the coordinator may wait indefinitely, causing delays and system hangs.

      3. Final Answer:

        The coordinator is waiting indefinitely for responses from crashed services -> Option A

      4. Quick Check:

        Waiting on crashed service = system hang [OK]
      Hint: Coordinator waits forever if service crashes [OK]
      Common Mistakes:
      • Thinking services commit too fast causes hangs
      • Believing skipping prepare phase causes delays
      • Assuming missing logs cause system hangs
      5. Why is two-phase commit often avoided in modern microservices architectures despite ensuring consistency?
      hard
      A. Because it causes blocking, reduces availability, and hurts scalability
      B. Because it does not guarantee data consistency
      C. Because it requires no coordination between services
      D. Because it is too simple and lacks fault tolerance

      Solution

      1. Step 1: Understand drawbacks of two-phase commit

        Two-phase commit blocks resources while waiting, reducing system availability and scalability.

      2. Step 2: Recognize why modern systems avoid it

        Modern microservices prefer eventual consistency and non-blocking patterns to improve performance and fault tolerance.

      3. Final Answer:

        Because it causes blocking, reduces availability, and hurts scalability -> Option A

      4. Quick Check:

        Blocking and low availability = avoid two-phase commit [OK]
      Hint: Two-phase commit blocks and limits scalability [OK]
      Common Mistakes:
      • Thinking it does not guarantee consistency
      • Believing it requires no coordination
      • Assuming it is too simple