Design a File Storage for Airbnb
Last updated: March 13, 2026
Quick Overview
Design a geo-distributed file storage system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Airbnb
March 13, 20266
3
2,042 solved
Design a geo-distributed file storage system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
This is a common system design question asked during Onsite at Airbnb. 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. Airbnb 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
- What would the deployment pipeline look like for this system?
- How would you handle schema migrations with zero downtime?
- How would you handle a 10x increase in traffic overnight?
- 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:
- File Upload & Download: Users should be able to upload and download files (images, documents) seamlessly.
- File Metadata Management: Store and retrieve metada...
Capacity Estimation
Back-of-Envelope Calculations:
- User Base: Assume 100 million users with an average of 5 files uploaded per user.
- Total Files: 100 million users * 5 files = 500 million files.
- **Fi...