Compare REST and gRPC for internal model-to-model calls.
PICTURE THIS: A REST CALL
ClientGET /users/1
ServerFind row
JSON back200 OK
Simple meaning
REST/JSON is simple to curl and debug
WHY — Model Serving instead of guessing?
Why interviewers care about Model Serving:
Model Serving questions separate
people who only read docs from people who shipped.
Keep it short, concrete,
and tied to MLOps work.
Stay structured
Name the idea, why it exists, then one short example.
Close cleanly
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:
- 1REST/JSON is simple to
curl and debug
- 2gRPC with protobuf is
faster, typed, and better for high QPS internals.
- 3Browser and partner clients
often still want HTTP.
- 4Many platforms offer both
from the same worker.
- 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:
Say this line
“Browser and partner clients often still want HTTP.”
Break into beats
Browserandpartnerclientsoftenstill
Speaking order
2987408337471632900
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
REST/JSON is simple to curl and debug gRPC with protobuf is faster, typed, and better for high QPS internals.