Architect a geo-distributed URL Shortening Engine
Last updated: May 27, 2026
Quick Overview
Design a geo-distributed url shortening system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Two Sigma
May 27, 20265
12
889 solved
Design a geo-distributed url shortening system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Two Sigma asks this during the Onsite to assess your architectural thinking. They want to see how you decompose a complex problem, choose appropriate technologies, and reason about failure modes. Strong candidates proactively discuss monitoring, alerting, and operational concerns.
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 optimize costs as the system scales?
- What monitoring and alerting would you set up on day one?
- How would you handle a 10x increase in traffic overnight?
- What would the deployment pipeline look like for this system?
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
- URL Shortening: The system must accept long URLs and return a shortened version.
- URL Redirection: When a shortened URL is accessed, the system must redirect t...
Capacity Estimation
Assuming Two Sigma expects around 10 million URL shortening requests per day:
- Requests per Second (RPS):
- 10 million requests per day / 86400 seconds = ~115.7 RPS.
- Storage Needs:
- ...
Submit Your Answer
