Design a large-scale Recommendation Platform

Last updated: November 9, 2025

Quick Overview

Design a scalable recommendation system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Airbnb
System Design
Software Engineer
Airbnb
November 9, 2025
Software Engineer
System Design Round
System Design
Medium

47

9

175 solved


Design a scalable recommendation system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

This is a common system design question asked during System Design Round 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
  • 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
High-level architecture and component design
Database selection and data modeling
Partitioning and sharding strategies
Requirements gathering and capacity estimation
How to Approach This
  1. Start by clarifying functional and non-functional requirements with the interviewer.
  2. Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
  3. Draw a high-level architecture first, then deep dive into 1-2 critical components.
  4. Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
  5. Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
  • How do you ensure data consistency across multiple services?
  • How would you handle a region-wide outage?
  • How would you handle schema migrations with zero downtime?
  • 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 Codemia
Sample Answer
Requirements

Functional Requirements

  1. User Preferences: Capture user preferences and behavior to provide personalized recommendations.
  2. Listing Attributes: Analyze listing features (e.g., location,...
Capacity Estimation

Estimation of Scale

  1. User Base: Assume 100 million active users on Airbnb.
  2. Daily Active Users (DAU): Assume 10% of users (10 million) access the recommendation system daily.
  3. **Requ...

Submit Your Answer
Markdown supported

Related Questions