Why do backend interviews treat two-phase commit as something to avoid?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
2PC holds locks across services and blocks if the coordinator dies, which kills availability.
WHY — Microservices instead of guessing?
Why interviewers care about Microservices:
on Microservices.
the situation, the default choice, and one exception - that reads as experience.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 12PC holds locks across
services and blocks if the coordinator dies, which kills availability.
- 2Latency and operational complexity
are high.
- 3Sagas and outboxes trade
immediate consistency for recovery you can actually operate.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
2PC holds locks across services and blocks if the coordinator dies, which kills availability. Latency and operational complexity are high.