Design Search Infrastructure for mobile apps
Last updated: April 26, 2026
Quick Overview
Design a low-latency search system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Airbnb
April 26, 2026137
12
508 solved
Design a low-latency search system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Airbnb asks this during the Technical Screen 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
- What happens if one of your database nodes goes down?
- What would the deployment pipeline look like for this system?
- How would you migrate from a monolithic to a microservices architecture?
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 Clarification
Before diving into the architecture, clarify the scope with the interviewer. For Search Infrastructure for mobile apps, key functional requirements in...
Capacity Estimation
Estimate the scale to drive design decisions. Assume 100M DAU with an average of 10 actions per user per day = 1B requests/day ~ 12K QPS average, ~36K...
Submit Your Answer
