Two-phase commit (and why to avoid it) in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main purpose of the two-phase commit protocol?

In a distributed system, what is the primary goal of using the two-phase commit protocol?

A To allow nodes to commit independently without waiting for others.

B To replicate data asynchronously across nodes for eventual consistency.

C To ensure all participating nodes agree to commit or abort a transaction, maintaining atomicity.

D To speed up transaction processing by parallelizing commits without coordination.

💡 Hint

Think about what atomicity means in transactions across multiple systems.

Two-phase commit ensures that either all nodes commit a transaction or none do, preventing partial commits.

❓ Architecture

intermediate

Which component coordinates the two-phase commit process?

In a two-phase commit protocol, which component is responsible for coordinating the commit or abort decision among participants?

A The coordinator node that sends prepare and commit/abort messages.

B Each participant independently decides when to commit.

C A load balancer that distributes requests evenly.

D A database replica that applies changes asynchronously.

💡 Hint

Consider who sends the 'prepare' message in the protocol.

The coordinator manages the transaction by asking participants if they can commit and then instructing them to commit or abort.

❓ scaling

advanced

Why does two-phase commit limit scalability in microservices?

Which of the following best explains why two-phase commit can reduce scalability in microservice architectures?

A It replicates data too quickly, overwhelming the network.

B It allows services to commit independently, increasing inconsistency.

C It uses asynchronous messaging that can lose data under load.

D It requires all services to lock resources and wait, causing delays and blocking.

💡 Hint

Think about what happens when multiple services wait for each other.

Two-phase commit forces all services to lock resources until the commit decision, causing blocking and reducing throughput.

❓ tradeoff

advanced

What is a major tradeoff when avoiding two-phase commit in distributed systems?

If a system avoids two-phase commit to improve performance, what is a common tradeoff it must accept?

A Accepting eventual consistency instead of strong atomic consistency.

B Guaranteeing immediate consistency but sacrificing availability.

C Increasing the risk of deadlocks due to resource locking.

D Reducing network latency by skipping message acknowledgments.

💡 Hint

Consider what consistency guarantees are relaxed when not using two-phase commit.

Avoiding two-phase commit often means systems accept eventual consistency to gain better performance and availability.

❓ estimation

expert

Estimate the impact of two-phase commit on transaction latency

Assume a distributed transaction involves 5 microservices communicating over a network with an average round-trip time of 50ms. Using two-phase commit, estimate the minimum additional latency introduced by the protocol before the transaction commits.

A About 50ms because only one message round-trip is needed.

B At least 100ms due to prepare and commit phases involving multiple message exchanges.

C Less than 50ms since messages are sent in parallel.

D No additional latency because commits happen instantly.

💡 Hint

Remember two-phase commit requires a prepare phase and a commit phase with message exchanges.

Two-phase commit involves at least two rounds of communication (prepare and commit) with all participants, adding multiple network delays.

Practice

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