Design StreamStay — StreamHub's travel booking platform (Airbnb-style): search listings by location and dates, book with payment hold, and manage host inventory. Date-range queries, booking conflicts, and payment holds are the core challenges.
Requirements
Functional requirements
- Search listings by location, check-in/check-out dates, guest count, and price range.
- View listing details: photos, amenities, reviews, availability calendar.
- Book a listing: hold dates, collect payment, confirm reservation.
- Host dashboard: manage listings, set pricing, block dates, view bookings.
- Guest dashboard: view upcoming and past reservations; cancel with policy.
- Review system: rate listing after checkout.
Non-functional requirements
- Scale: 50M users; 5M listings; 500K bookings/day.
- Search latency: Results under 500 ms p99.
- Booking consistency: Zero double-bookings — strong consistency on date holds.
- Payment: Authorise on book, capture 24 h before check-in; idempotent.
- Availability: 99.9% for search and booking paths.
Out of scope: Dynamic pricing ML, insurance, multi-currency FX, host verification workflow.
Estimation
- 500K bookings/day × 365 = 182M bookings/year × 500 bytes ≈ 91 GB/year reservation storage.
- 5M listings × 365 days availability = 1.8B date-slots — bitmap or row-per-date model.
- Search: 50M users × 5 searches/day = 250M searches/day ≈ 2.9K QPS — Elasticsearch with geo queries.
- Payment holds: 500K/day ≈ 6 QPS — Stripe auth/capture pattern with idempotency.
Hotel reservation architecture
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 5 sections
- API design
- High-level architecture
- Deep dive: availability and double-booking prevention
- Deep dive: booking saga with payment hold
- Deep dive: geo search
Test yourself
Answer these before moving on — recall is what makes it stick.