Design a geo-distributed Search System
Last updated: March 17, 2026
Quick Overview
Design a geo-distributed search system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Spotify
System Design
Software Engineer
Spotify
March 17, 2026Software Engineer
Onsite
System Design
Medium
46
13
2,553 solved
Design a geo-distributed search system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Spotify 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
- Systematically gather requirements and estimate capacity (QPS, storage, bandwidth)
- Design a scalable architecture with clear component responsibilities
- Make well-reasoned database and caching decisions with trade-off analysis
- Address consistency vs availability trade-offs specific to the use case
- Discuss partitioning strategy, replication, and data modeling
- Cover failure handling, monitoring, and alerting strategies
Key Topics to Cover
Failure handling and fault tolerance
API design and rate limiting
Caching strategies (local, distributed, CDN)
High-level architecture and component design
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?
- What happens if one of your database nodes goes down?
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:
- Users can perform text-based searches for songs, albums, and artists.
- The system must return relevant results quickly, ideally within 200ms.
- Support fo...
Capacity Estimation
- Estimated QPS:
- Assume Spotify has 500 million active users, with an average of 10 searches per user per day.
- Total daily searches = 500M users * 10 searches/user = 5 billion searches...
Submit Your Answer
Markdown supported