When would you serve predictions in batch, and when online?
Deployment and LLMOps · Pro 1
Short answer
Batch scoring runs on a schedule over many records and stores the results, which is cheap and simple when predictions can be a few hours old, such as nightly churn scores. Online serving computes a prediction per request behind an API, needed when the answer depends on fresh input, such as fraud checks at payment time.
Deeper answer
Ask how fresh the prediction must be and how many entities there are. Recommendations for millions of users can be precomputed nightly; a search ranking that depends on the query cannot.
Online serving needs a model server, features available at request time (often a feature store to keep training and serving features consistent), a latency budget, autoscaling and fallbacks. A common hybrid precomputes heavy features in batch and does a light model call online.
What a strong answer covers
- Batch: scheduled, stored results, cheaper
- Online: per request behind an API
- Decide by how fresh the prediction must be
- Online needs latency budget, scaling and fallbacks
- Training-serving consistency or feature store
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- What is training-serving skew, and how do you avoid it?
- How would you add a fallback if the model server is down?
Common mistakes
- Choosing online serving when batch would do
- Computing features differently in training and serving
Learn it
- How would you set up CI/CD for an LLM application?
- What is the difference between data parallelism and model parallelism?
- Why does experiment tracking matter, and what do you record?
- Your model scored well offline but performed badly after launch. What could explain it?
- Explain Kubernetes pods, deployments and services, and why you would use Kubernetes for AI apps.
- What is the KV cache, and why can it cause out-of-memory errors when serving an LLM?
- How would you load test an LLM feature and set a latency budget?
- Your model provider has an outage during peak hours. What should already be in place?
- How do you manage API keys and secrets across environments?
- How do you detect and handle model drift in production?
- A bank wants your AI system but says no data may leave its network. What are the options?
- Why does an LLM reply have a wait before the first word and then a different speed after it?
- What is quantisation, and what are the trade-offs?
- When would you use a semantic cache for an LLM app, and what can go wrong?
- How would you serve an LLM feature as an API for a web app?
- How would you serve a model that is too big for one GPU, and how would you scale it to more users?
- How would you add single sign-on to an enterprise AI assistant?
- How do you version prompts and models so you can roll back safely?
- What would you capture in traces for an LLM application?
- Why use Docker for an AI application?
- What does an LLM gateway do, and when do you need one?
- Why use vLLM to serve an open-weight model instead of a simple Hugging Face script?