Design a scalable URL Shortening System
Last updated: August 19, 2025
Quick Overview
Design a scalable url shortening system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Snowflake
August 19, 202555
13
1,272 solved
Design a scalable url shortening system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
System design interviews at Snowflake typically last 45-60 minutes. You are expected to drive the conversation, starting from requirements gathering through to a detailed architecture. The interviewer will evaluate your ability to handle ambiguity and make practical engineering decisions.
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 handle a 10x increase in traffic overnight?
- What happens if one of your database nodes goes down?
- How would you handle a region-wide outage?
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
- Shorten URL: Users can submit a long URL and receive a shortened version.
- Redirect: When a user accesses the shortened URL, they should be redirected to the o...
Capacity Estimation
Assuming the system needs to handle 10 million requests per day:
- Total Requests per Second: 10 million requests / 86400 seconds ≈ 115.74 requests/second.
- Average URL Length: Assuming an av...
Submit Your Answer
Snowflake Machine Learning Engineer Interview Guide
Interview process, tips, and preparation timeline