Layer 3 · Go deeper · 5 min
Go deeper
Size it, build it, then make the calls an interviewer will push you on.
Back of the envelope
Size it up
Tap through each step of the arithmetic.
Build-up · 6 steps
Split one shared Order into contexts
Imagine four food-delivery teams sharing one Order table. Watch it split into bounded contexts, each with its own model, wired by one call and events.
Step 1 of 6
One Order table for everyone
Every team reads and writes one shared Order table. Each new field needs every team to agree, and nobody can change their process without asking the others.
4 interview moments
You’re the candidate
The interviewer pushes on the hard parts. Pick an approach and see how it holds up.
Deep dive 1 of 4
Interviewer
“You’re splitting a Swiggy-style food-delivery app into services. How do you draw the boundaries?”
Your move. Pick an approach:
Deep dive 2 of 4
Interviewer
“Placing an order must also create the restaurant’s kitchen ticket. Do you put both in one transaction?”
Your move. Pick an approach:
Deep dive 3 of 4
Interviewer
“Payments must talk to an external payment gateway and finance’s legacy ERP. How do you integrate them?”
Your move. Pick an approach:
Deep dive 4 of 4
Interviewer
“Every feature changes your Order and Payment services together, and each request calls between them several times. What now?”
Your move. Pick an approach: