Summary
30-second pitch
Compensating transaction as a single transcation cannot cross service (domain ?) boundary
Hook:
Orchestrator — a mnemonic, analogy, or phrase
Choreographer
How it works (Mental Model)
Brief explanation of the mechanism.
The “Gotcha” (Interview Bait)
Common trap
The non-obvious behaviour or classic mistake, and why people get it wrong.
Trade-offs
- Pros: when to reach for this.
- Cons: what you give up.
Real-world Scenario
“At [company/project] we used this to solve Y.” No direct experience? Frame it as
a design requirement: “If I were building X, I’d use this because…”
Interviewer’s Follow-up
Anticipate the next question
e.g. “If I asked you to scale this 10x, what breaks first?”
Quick References
Test Yourself
Question
A: [the answer you should be able to give]
Question
A: [the answer]