System design interview guide
Airbnb System Design Interview: Search, Availability, and the Race to Book the Same Listing
Short answer
Airbnb system design splits into two workloads. Search is read heavy: a guest's place and dates filter millions of listings in a separate index such as Elasticsearch, updated asynchronously, so it is eventually consistent by design. Booking is the hard part: two guests can reserve the same listing for overlapping nights at the same instant, so reservations live in a strongly consistent store sharded by listing, with row-level locking or optimistic concurrency on the calendar and short-lived holds during checkout. Payments split the guest charge from a delayed host payout, with idempotency so a retry never charges twice.
Two courses by the author of this page:
770 lessons · 18 free to read
₹1,111 in India · $35 elsewhere, once
Get System DesignYou own this course
219 lessons · 10 free to read
₹1,333 in India · $35 elsewhere, once
Get Generative AI and Agentic AIYou own this course
Save your progress and get the interview checklist PDF
Airbnb has reported more than 8 million active listings and over 5 million hosts, with cumulative guest arrivals passing 2 billion. The hard part is not the raw traffic. It is that a single home can accept exactly one guest for a given set of nights, so search is enormously read heavy while the booking write path has to stay strictly consistent under contention. Most scale numbers below are estimates derived from public figures unless marked as published.
Airbnb is a two sided marketplace where hosts list homes and guests search, book, and pay. A guest types a place and a date range, and the system filters millions of listings by location, dates, price, guest count, and amenities, then ranks them with personalization, all in a couple hundred milliseconds. The genuinely hard subsystem is the booking write path: two guests can try to reserve the same listing for overlapping dates at the same instant, and the design must let exactly one of them win. That means a strongly consistent reservation store, usually a relational database sharded by listing, with row level locking or optimistic concurrency on the calendar, plus short lived holds during checkout. Search runs off a separate denormalized index such as Elasticsearch that is updated asynchronously from booking and calendar events, so search is eventually consistent by design while reservations are not. Payments split a guest charge from a delayed host payout and hold funds until after check in, which forces careful idempotency so a retried request never charges twice. The whole thing is a study in choosing where to pay for strong consistency and where eventual consistency is fine.
Where it shows up
Asked at Airbnb, Booking.com, Uber, DoorDash, and most large product companies as the canonical booking and reservation problem. It also shows up framed as design a hotel reservation system or design an event ticketing system.
Spec sheetAirbnb
- 01Active listings
- 8M+ (published)
- 02Search QPS
- ~15K-30K peak (Derived estimate)
- 03Bookings per day
- ~1M-2M (Derived estimate)
- 04Read to write ratio
- ~1000:1 or higher (Derived estimate)
worked through below, with the maths
in this guide
Design Airbnb, part by part
7 parts open to everyone · 3 with a free account · 3 with the course
You can read 7 of 13 parts. A free account opens the deep dive; the course opens all of it.
- Requirementsopen
- Scale estimatesopen
- High-level architectureopen
- Core componentsopen
- Data modelfree account
- Deep dives (7)free account
- Trade-offs to discussfree account
- What the interviewer asks nextwith the course
- The interview scorecardwith the course
- Mock interview on this questionwith the course
- How Airbnb actually does itopen
- Frequently asked questionsopen
- Interview readiness checkopen
The hard parts of this design are taught step by step in the System Design course: Geospatial Indexing, Idempotency Keys and Distributed Locks.
Why this question is asked
Interviewers like Airbnb because it forces a candidate to reason about two workloads with opposite requirements in the same system. Search is read heavy, latency sensitive, and tolerant of staleness, which pushes you toward denormalized indexes and caching. Booking is write heavy per listing, contended, and intolerant of any double sell, which pushes you toward strong consistency and locking. A strong candidate names that split early, then defends where they place transactions, how they prevent the overlapping date race, how listings flow from the source of truth into the search index, and how the payment split stays idempotent. It tests data modeling, concurrency control, and event driven propagation all at once.
This page is the free part.
The course goes deeper on the Airbnb design
₹1,111 in India$35 everywhere elseonce, for the whole course
The System Design course covers the Airbnb design across a run of lessons, not one page. These 4 alone are about 108 minutes of step-by-step reading, 1 of them with code you run in the browser, all with a quiz.
- Database Sharding
Splitting a database across multiple servers, the nuclear option for scaling writes, and the architecture behind Instagram, Uber, and YouTube.
- Idempotency Keys
Safely retry failed API requests without causing duplicate side effects.
- Saga Pattern
Long-lived transactions without distributed locking, orchestration vs choreography for microservices.
- Snapshot Isolation
Snapshot isolation, explained: each transaction reads one frozen view of the data. How MVCC builds it, the write skew it allows, and the Postgres fix.
all part of
System Design Masterclass
770 lessons · about 290 hours · 18 free to read
₹1,111in India, by UPI
$35everywhere else, by card or PayPal
You own this course
Continue with Database Shardingpay once,
yours for life
Live from the course bench
Before you design Airbnb, try the questions it rests on.
Real interview questions, live diagrams and measured lab results, pulled at random from the lessons. A new set every time you come back.
Requirements
Always clarify these in the first 5 minutes of the interview. Do not start drawing boxes until both lists are agreed.
Functional requirements
- Guests search listings by location or map bounding box, date range, guest count, price, and amenity filters
- Rank and personalize results using listing quality, relevance, and the guest's recent session behavior
- Hosts create and edit listings, set nightly prices and rules, and manage a calendar of available dates
- Show accurate per night availability and total price including cleaning fees, service fees, and taxes
- Let a guest place a reservation for a listing and date range without ever double booking
- Charge the guest, hold the money, and pay the host out after check in, across currencies
- Support messaging between host and guest and two sided reviews after a completed stay
- Send booking confirmations, reminders, and cancellation or refund flows
- Let hosts and guests cancel subject to the listing's cancellation policy
Non-functional requirements
- Search results in roughly 200 ms at the 99th percentile for interactive feel
- Zero double bookings, the booking write path must be strongly consistent
- High availability for search and browsing, degrade gracefully if ranking is slow
- Search index may lag the source of truth by seconds, that staleness is acceptable
- Payments must be exactly once in effect, a retry can never charge a guest twice
- Horizontally scalable reads, the read to write ratio is very lopsided
- Global low latency, guests and listings span many regions and currencies
- Durable audit trail for money movement and reservation state changes
Back-of-envelope scale estimates
Show your math. Pulling numbers from thin air signals you have not thought about the load.
Active listings
8M+ (published)
Airbnb has publicly reported more than 8 million active listings. Even at a few kilobytes of core metadata each, the primary listing set is only tens of gigabytes, so the challenge is query patterns and the calendar, not raw listing size.
Search QPS
~15K-30K peak (Derived estimate)
Assume roughly 150M monthly active searchers doing a handful of searches per active session, concentrated in evenings and weekends. Spreading a few hundred million searches per day over a day with a 5x to 10x peak factor lands in the low tens of thousands of queries per second. Derived, not published.
Bookings per day
~1M-2M (Derived estimate)
Cumulative guest arrivals have passed 2 billion over Airbnb's lifetime. Recent annual nights and experiences booked are in the hundreds of millions, so on the order of one to two million confirmed bookings per day. This makes write TPS modest, low tens per second on average, but heavily skewed to popular listings and dates.
Read to write ratio
~1000:1 or higher (Derived estimate)
Tens of thousands of searches per second against low tens of bookings per second gives a ratio well past a thousand to one. This asymmetry is the reason search and booking are split into separate systems with separate stores.
Availability rows
Billions (Derived estimate)
8M listings times a booking window of roughly 365 to 500 future days, if you model availability one row per listing per day, is on the order of 3 to 4 billion calendar rows. A range based representation shrinks this a lot, which is one reason range models are attractive.
Payment records
Hundreds of millions per year (Derived estimate)
Each booking generates at least a guest charge and a host payout, plus refunds and adjustments, so a year of bookings produces several hundred million money movement events that all need idempotency keys and an audit trail.
High-level architecture
A guest request lands at an edge and API gateway that fans out to backend services, an approach Airbnb moved to as it broke its Rails monolith into service oriented architecture. Browsing and search hit a read path: the search service queries a denormalized listing index, typically Elasticsearch, that supports geospatial filtering by bounding box or radius plus structured filters on price, guests, and amenities. Candidate listings are then scored by a ranking service that layers in personalization from the guest's recent session, and results, minus anything already booked for the requested dates, come back within a couple hundred milliseconds. When the guest picks a listing and dates, they cross into the write path. The reservation service checks the availability calendar in a strongly consistent relational store, places a short lived hold on those nights so the guest can finish checkout, and confirms the reservation inside a transaction that flips the calendar to booked. The payment service then charges the guest through a payment orchestration layer, records the money movement idempotently, and schedules the host payout for after check in. Every state change that matters to search, a new listing, an edited price, a calendar update, or a completed booking, is published as an event onto a bus such as Kafka. An indexing pipeline consumes those events and updates Elasticsearch asynchronously, which is why search is eventually consistent while the reservation store is the source of truth.
In a real interview, sketch this on the whiteboard before diving into any single box.
Core components
Walk through each service. The interviewer wants to hear what each one owns, not just the names.
Search and geo service
Serves the read heavy query path against a denormalized index like Elasticsearch that combines geo queries with structured filters. It resolves a map bounding box or a place plus radius, applies date, price, guest, and amenity filters, and returns a candidate set fast. It is built to scale out by adding nodes and replicas independently of the booking system.
Ranking and personalization service
Takes the candidate listings from search and orders them using listing quality signals and real time personalization. Airbnb has published work on listing and user embeddings that push listings similar to ones the guest engaged with this session up, and ones they skipped down. This is where machine learning models and feature stores live.
Listing and calendar service
The host facing source of truth for listing content, pricing rules, and per date availability. Hosts edit listings and block or open dates here. Every mutation is written transactionally and emitted as an event so the search index and pricing can catch up.
Reservation and booking service
Owns the strongly consistent write path. It validates that the requested nights are free, places a temporary hold during checkout, and commits the booking in a transaction that also marks the calendar. This is where double booking is prevented with locking or optimistic concurrency.
Pricing service
Computes the total a guest sees: nightly price for each date, any host set weekend or seasonal adjustments or smart pricing suggestions, cleaning and service fees, taxes, and currency conversion. It reads calendar and rules and returns a priced quote that the booking flow reuses.
Payments and payout orchestration
Splits the guest charge from the host payout and holds funds until after check in, acting as an escrow style intermediary. It integrates external processors and uses an idempotency framework so retries never double charge. Airbnb built Orpheus for exactly this.
Indexing and event pipeline
Consumes listing, calendar, and booking events from Kafka and updates the Elasticsearch index and downstream caches. This decouples the write systems from search so each scales on its own, at the cost of a few seconds of index staleness.
Data model
listings. Source of truth for listing content and location, sharded by listing_id or host_id. Attributes such as amenities and property type live in a flexible column and are…
Every table for Airbnb, its keys, and which store fits it and why.
Deep dives
Preventing the double booking race. Two guests can hit confirm on the same listing for overlapping nights within milliseconds of each other. The read heavy search path can be eventually consistent, but…
7 deep dives on the parts that break at scale: Preventing the double booking race; Holds during checkout; Geospatial search with filters.
Trade-offs to discuss
Separate search index versus querying the booking database directly. A denormalized Elasticsearch index gives fast geo and filter queries and scales reads on its own, at the price of eventual consistency. Querying the transactional store…
6 decisions an interviewer expects you to defend, each with the alternative and why it loses here.
What the interviewer asks next
The background sweeper that expires checkout holds crashes for an hour. Do listings stay blocked?
4 follow-up questions with model answers, the interview scorecard for this question, and a mock interview on Design Airbnb with the AI tutor.
How Airbnb actually does it
Airbnb started as a Ruby on Rails monolith and moved to service oriented architecture as it grew, adopting SmartStack for service discovery and running MySQL on RDS with proxies for connection pooling and throttling. The team has written about partitioning its main database to scale writes. On search, Airbnb published a KDD 2018 paper on real time personalization using listing and user embeddings, collecting clicked and skipped listings via Kafka to personalize ranking within a session, and later work on embedding based retrieval. On money, Airbnb built the Orpheus idempotency framework to avoid double payments in its distributed payment system, splitting each request into pre RPC, RPC, and post RPC phases with a row level lock on the idempotency key, and reported reaching five nines of payment consistency as volume doubled. They later wrote about rebuilding payment orchestration. Airbnb also created Apache Airflow to schedule the batch and data pipelines behind pricing and analytics.
Lessons to study before this interview
If any of these topics are fuzzy, the interviewer will catch it. Each lesson is 15 to 60 minutes with diagrams, code, and a quiz.
System design interviews at companies in the US, UK, Canada and Singapore
41 walkthroughs of real systems at well-known companies, each built from that company's own engineering blog, talks or filings, with the numbers cited.
Banking, payments and trading
Commerce and delivery
- Shopify system design (Canada)
- DoorDash system design
- Amazon system design
- Airbnb system design (this page)
- Agoda system design (Singapore)
- Uber Eats system design
Rides and maps
- Grab system design (Singapore)
- Uber system design
Feeds, social and messaging
Streaming and media
AI labs and big tech
Developer and collaboration tools
Frequently asked questions
interview readiness
Are you ready for Design Airbnb?
Three questions from this guide. Answer them without scrolling up, the way you would have to in the room.
Go deeper
This guide is built on these 5 lessons. Each one teaches one piece of the Airbnb design above, step by step.
- Database ShardingSystem Design · database fundamentals · 35 min
- Idempotency KeysSystem Design · api design protocols · 18 min
- Saga PatternSystem Design · distributed systems core · 30 min
- Snapshot IsolationSystem Design · consistency models · 25 min
- Change StreamsSystem Design · stream batch processing · 38 min
Practice with 770 system design lessons
Lifetime access for ₹1,111 in India or $35 elsewhere. Interactive diagrams, quizzes, and 20 capstone projects to practise on.
This one question is not enough for the interview.
Get all 200 questions in the System Design and Distributed Systems pack
Each question has why it is asked, a full answer, what the interviewer listens for, the follow-ups, the common mistakes and a diagram (268 diagrams in all). A PDF you keep, junior to staff level.
Pay by UPI, cards or netbanking through Razorpay. Pay by card or PayPal, in US dollars. Download at once from My packs.
NEWSystem Design Hands-On
Included in the System Design course: real systems, built live
Postgres Sharding: Complete Hands-On (PgBouncer + Citus). 2 h 36 min and 20 chapters: one PostgreSQL loaded until it breaks, then four shards behind a router you write, PgBouncer and Citus, with the 139-page slide deck. The first 15 minutes are free to watch.


