Design a Ride Matching Service
Last updated: June 7, 2026
Quick Overview
Design a geo-distributed ride matching system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Airbnb
June 7, 202634
9
3,351 solved
Design a geo-distributed ride matching 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 happens if one of your database nodes goes down?
- How do you ensure data consistency across multiple services?
- How would you handle schema migrations with zero downtime?
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:
- Match riders with nearby drivers in real-time based on geolocation.
- Allow users to request rides, track ride status, and make payments.
- Provide a user interf...
Capacity Estimation
Assuming Airbnb operates in major cities globally and handles approximately 10 million ride requests per day:
- Requests Per Second (RPS):
- 10 million requests/day = 115.74 requests/second.
- ...
Submit Your Answer
