Two-phase commit (and why to avoid it) in Microservices - Scalability & System Analysis

Scalability Analysis - Two-phase commit (and why to avoid it)

Growth Table: Two-phase commit in microservices

Users / Transactions	System Behavior	Impact on Two-phase Commit
100 users	Low concurrency, few distributed transactions	Two-phase commit (2PC) works reliably with minimal delays
10,000 users	Moderate concurrency, more distributed transactions	2PC latency increases; blocking locks start to affect throughput
1,000,000 users	High concurrency, many distributed transactions	2PC causes significant delays; coordinator becomes bottleneck; risk of deadlocks and timeouts rises
100,000,000 users	Very high concurrency, massive distributed transactions	2PC is impractical; system stalls; availability and scalability severely impacted

First Bottleneck

The transaction coordinator in the two-phase commit protocol becomes the first bottleneck. It must wait for all participants to prepare and then commit or abort, causing blocking. As concurrency grows, the coordinator's CPU and network become overwhelmed, leading to increased latency and potential deadlocks.

Scaling Solutions

• Avoid 2PC: Use eventual consistency and compensation patterns to reduce blocking.
• Event-driven architecture: Replace distributed transactions with asynchronous messaging and retries.
• Idempotent operations: Design services to safely retry without strict locking.
• Partition data: Minimize cross-service transactions by data ownership boundaries.
• Use Saga pattern: Manage distributed transactions as a sequence of local transactions with compensations.
• Horizontal scaling: Scale microservices independently to handle load, but avoid scaling 2PC coordinator as it is a single point of failure.

Back-of-Envelope Cost Analysis

Assuming 1,000 QPS of distributed transactions:

• Each 2PC transaction involves multiple network round-trips (prepare + commit phases), doubling or tripling latency.
• Coordinator CPU and memory usage grows linearly with concurrent transactions; at 10,000 QPS, coordinator CPU saturates.
• Network bandwidth increases due to coordination messages; at 1M QPS, network becomes a bottleneck.
• Storage locks held during 2PC increase transaction duration, reducing throughput.

Interview Tip

When discussing scalability of two-phase commit, start by explaining how 2PC works and why it blocks. Then identify the coordinator as the bottleneck. Next, discuss how latency and blocking grow with traffic. Finally, propose alternatives like Saga or event-driven approaches to improve scalability and availability.

Self Check

Your database handles 1000 QPS with two-phase commit. Traffic grows 10x. What do you do first?

Answer: The first step is to avoid or reduce two-phase commit usage because the coordinator and locking will become bottlenecks. Implement eventual consistency patterns like Saga to break distributed transactions into smaller local transactions with compensations, improving throughput and reducing blocking.

Key Result

Two-phase commit blocks distributed transactions and becomes a bottleneck as concurrency grows; replacing it with eventual consistency patterns like Saga improves scalability and availability.

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