Walk through choreography versus orchestration sagas for place-order.
PICTURE THIS: RAG CHATBOT
Simple meaning
Choreography: OrderPlaced triggers Inventory to reserve
WHY — Microservices instead of guessing?
Why interviewers care about Microservices:
contrast on Microservices, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
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:
- 1Choreography: OrderPlaced triggers Inventory
to reserve
- 2Why it exists
InventoryReserved triggers Payment.
- 3It is decoupled but
hard to see the whole flow.
- 4Orchestration: an order saga
service commands each step and records state.
- 5Product teams often orchestrate
payments because the happy path and refunds need an explicit state machine.
- 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
Choreography: OrderPlaced triggers Inventory to reserve InventoryReserved triggers Payment.