Design a geo-distributed Content Delivery System
Last updated: August 27, 2025
Quick Overview
Design a geo-distributed content delivery system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
NVIDIA
August 27, 202540
12
2,005 solved
Design a geo-distributed content delivery system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
This is a common system design question asked during Technical Screen at NVIDIA. The interviewer expects you to demonstrate your ability to design large-scale distributed systems, make well-reasoned trade-offs, and communicate your thought process clearly. NVIDIA values engineers who can think about scalability from day one.
What the Interviewer Expects
- Clearly define functional and non-functional requirements
- Propose a reasonable high-level architecture with core components
- Choose appropriate data storage solutions with basic justification
- Discuss basic scaling strategies (horizontal scaling, caching)
- Identify potential bottlenecks and suggest simple solutions
Key Topics to Cover
How to Approach This
- Start by clarifying functional and non-functional requirements with the interviewer.
- Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
- Draw a high-level architecture first, then deep dive into 1-2 critical components.
- Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
- Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
- What monitoring and alerting would you set up on day one?
- How would you handle a region-wide outage?
- What would the deployment pipeline look like for this system?
- How would you optimize costs as the system scales?
Practice a Similar Problem on Codemia
Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.
Solve on CodemiaSample Answer
Requirements
- Functional Requirements:
- Support for geo-distributed content delivery to ensure low latency access for users around the globe.
- Ability to handle millions of concurrent requests with dyna...
Capacity Estimation
- Assume 10 million daily active users accessing content.
- If each user makes an average of 10 requests per day, that results in 100 million requests per day.
- Breaking that down to per second:
- ...