Design scalable, highly available GenAI serving

Read the full interview experience this question came from →

Quick Overview

This question evaluates understanding of scalable, highly available generative AI inference platforms and associated competencies in distributed systems, ML model serving, autoscaling and GPU scheduling, global request routing, model/version management, stateful dependency handling, observability, and rate limiting.

Design scalable, highly available GenAI serving

Company: Oracle

Role: Software Engineer

Category: ML System Design

Difficulty: hard

Interview Round: Onsite

Design the deployment of a generative AI model for high scalability and high availability. Describe the inference serving architecture, request routing, autoscaling (including GPU scheduling), multi-region failover, model versioning and rollout, stateful dependency management (tokenizer, embeddings, caches), observability, rate limiting, and strategies to meet latency/throughput SLOs under traffic spikes and failures.

Overview: This question evaluates understanding of scalable, highly available generative AI inference platforms and associated competencies in distributed systems, ML model serving, autoscaling and GPU scheduling, global request routing, model/version management, stateful dependency handling, observability, and rate limiting.

Read the full Oracle Software Engineer interview experience this question came from

Community answers

Answer by jimmyp

| > Design Decision | > What We Gained (Benefit) | > What We Sacrificed (Cost / Trade-off) | > Mitigation Strategy | | --- | --- | --- | --- | | > > Continuous Batching vs. Static Batching | Up to > $10\times$ higher overall throughput and significantly lower p95 latency for short sequences. | > Higher CPU scheduling overhead and complex asynchronous memory management. | > Use high-performance C++/CUDA schedulers (vLLM/TensorRT-LLM) bound to dedicated CPU cores. | | > > Cache-Aware Routing vs. Round-Robin | > > 60–80% reduction in prefill compute , drastically reducing TTFT for shared system prompts. | > Risk of hot-spotting specific worker pods if one system prompt becomes wildly popular. | > Enforce bounded-load consistent hashing; spill overflow traffic to secondary pools if node queue > $> 50\text{ ms}$ . | | > > Multi-LoRA Serving vs. Dedicated Endpoints | > Ability to serve > hundreds of custom fine-tuned models from a single GPU pool, saving millions in hardware costs. | > Slight latency penalty ( > $\approx 10\text{ ms}$ ) when swapping LoRA weights from host RAM into GPU HBM for infrequent tenants. | > Cache top-10 most active LoRA adapters permanently in GPU High-Bandwidth Memory (HBM). | | > > Speculative Decoding vs. Standard Decode | > > > $1.5\times - 2\times$ > faster token generation speed (TPOT) without loss of quality. | > Consumes additional VRAM to host the draft model and increases complexity in the inference engine. | > Dynamically disable speculative de
|Home/ML System Design/Oracle
Oracle logo
Oracle
Sep 6, 2025
hardSoftware EngineerOnsiteML System Design
3
0

System Design: Highly Scalable, Highly Available Generative AI Inference Platform

Context

Design a production-grade deployment for a generative AI text model (decoder-only Transformer, 7B–70B parameters) serving enterprise, multi-tenant traffic. The platform must sustain high scalability and high availability across regions and handle unpredictable traffic spikes.

You may make minimal, explicit assumptions to ground your design (e.g., target SLOs for time-to-first-token and throughput, typical prompt/output lengths, GPU types).

Requirements

Describe and justify your design for the following:

  1. Inference serving architecture
    • Components and data/control planes
    • Streaming vs non-streaming; batching; cache usage
  2. Request routing
    • Global and regional routing, session affinity, retries/hedging
  3. Autoscaling (including GPU scheduling)
    • Replica scaling signals, node autoscaling, bin-packing/MIG, warm pools
  4. Multi-region strategy
    • Active-active vs active-passive, failover triggers, data/control plane considerations
  5. Model versioning and rollout
    • Registry, artifact management, canary/blue-green, rollback, compatibility (tokenizer/adapters)
  6. Stateful dependency management
    • Tokenizer/embeddings versioning, KV/prompt caches, locality/affinity, external stores
  7. Observability
    • Metrics/traces/logs at model/tenant/version levels; GPU health; SLO dashboards and alerting
  8. Rate limiting and fairness
    • Per-tenant budgets, token-based limits, concurrency caps, overload protection
  9. Meeting latency/throughput SLOs under spikes and failures
    • Admission control, dynamic batching, speculative decoding, degradation and fallbacks

Provide a clear end-to-end flow and the key trade-offs behind your choices.

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...