Consumer & Marketplace: Flash Sale (Big Billion Days), Price Tracker & Alerts (CamelCamelCamel), Tinder, News Aggregator (Google News) & Strava

Five consumer designs that each hide one hard problem: selling 50K units to 5M people in a minute without overselling or rewarding bots, matching millions of price rules without spamming anyone, detecting a mutual like exactly once, turning 3M articles a day into a few hundred stories, and timing an athlete over a GPS trace that never lies on the segment.

About 200 minutes · 18 exam questions · 14 interview questions · 2 code labs

What you will learn

  1. Flash sale (1/3): requirements, estimation, API & data model
  2. Flash sale (2/3): architecture — admission, bucketed Redis gate & async orders
  3. Flash sale (3/3): durable claim, oversell under failover, fairness & bots
  4. Price tracker & alerts (1/3): requirements, estimation, API & data model
  5. Price tracker & alerts (2/3): change detection & rule matching at scale
  6. Price tracker & alerts (3/3): fan-out, throttling, digests & trade-offs
  7. Tinder (1/3): requirements, estimation, API & data model
  8. Tinder (2/3): swipes & exactly-once match detection
  9. Tinder (3/3): geosharded recommendations & never re-showing a profile
  10. News aggregator (1/3): requirements, estimation & the ingestion pipeline
  11. News aggregator (2/3): near-duplicate detection & story clustering
  12. News aggregator (3/3): ranking, personalisation, freshness & serving
  13. Strava (1/3): requirements, estimation & activity ingestion
  14. Strava (2/3): segment matching — finding every segment a GPS trace rode
  15. Strava (3/3): leaderboards, the activity feed, privacy & trade-offs
  16. Level bar: what mid, senior and staff answers include
  17. Deep-dive ladders: bad → good → great

Previous: More Classics: Web Crawler, Top-K / Trending, Distributed Counters (Likes & Views), Online Judge (LeetCode) & Online Auction (eBay) · Next: Platform, Fintech & AI: Robinhood-style Brokerage, CI/CD Runner (GitHub Actions), Online Chess Server, Calendar & Scheduling (Google Calendar / Calendly) & RAG Document Q&A