Build a low-latency Content Delivery Pipeline
Last updated: November 18, 2025
Quick Overview
Design a low-latency content delivery system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Stripe
November 18, 202571
13
3,643 solved
Design a low-latency 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 Stripe. 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. Stripe 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
- How would you migrate from a monolithic to a microservices architecture?
- What happens if one of your database nodes goes down?
- What monitoring and alerting would you set up on day one?
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:
- Content Ingestion: Ability to accept content from various sources (e.g., APIs, manual uploads).
- Content Delivery: Serve static and dynamic content with low l...
Capacity Estimation
Assuming Stripe has approximately 1 million active users:
- Requests per Second (RPS): If each user generates 1 request every 2 seconds, we can estimate:
- Total RPS = 1,000,000 users / 2 seco...
Submit Your Answer
