You split orders and inventory into two databases. How do you avoid a distributed two-phase commit?
PICTURE THIS: DATABASE INDEX
Simple meaning
Do not start a global XA transaction across services.
WHY — Microservices instead of guessing?
Why interviewers care about Microservices:
who only read docs from people who shipped.
and tied to Backend work.
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:
- 1Do not start a
global XA transaction across services.
- 2Use a saga: local
transactions plus compensating actions, or an outbox so the order row and the event commit together.
- 3Accept eventual consistency and
design APIs that can retry safely.
- 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
Do not start a global XA transaction across services. Use a saga: local transactions plus compensating actions, or an outbox so the order row and the event commit together.