Location Systems: Proximity Service, Nearby Friends, Google Maps & Uber
Geospatial indexing, real-time location fan-out, map tiles and routing, and ride-hailing dispatch — the designs where "where is it?" meets "how fast can I answer?".
About 160 minutes · 15 exam questions · 8 interview questions · 2 code labs
What you will learn
- Proximity Service (1/3): requirements, estimation, API & data model
- Proximity Service (2/3): geospatial indexes — grid, geohash, quadtree, S2 & H3
- Proximity Service (3/3): architecture, scaling, caching & wrap-up
- Nearby Friends (1/3): requirements & the fan-out math
- Nearby Friends (2/3): architecture — WebSocket servers, location cache & Redis pub/sub
- Nearby Friends (3/3): scaling the WebSocket and pub/sub tiers
- Google Maps (1/3): requirements, estimation & map tiles
- Google Maps (2/3): road graph, routing tiles, shortest path & ETA
- Google Maps (3/3): location ingestion, adaptive ETA & rerouting, wrap-up
- Uber (1/3): requirements, estimation & driver location ingestion
- Uber (2/3): matching & dispatch without double-booking drivers
- Uber (3/3): trip state machine, surge pricing, tracking & payments
- Food delivery (Swiggy / Zomato / DoorDash) — the three-sided variant
- Bottlenecks, trade-offs & wrap-up across location systems
- Level bar: what mid, senior and staff answers include
- Deep-dive ladders: bad → good → great
Previous: Classic Designs: URL Shortener, Pastebin, KV Store, Unique IDs & Notifications · Next: Social & Media: Chat/WhatsApp, News Feed (Twitter/Instagram) & YouTube/Netflix