Separate ingest from matching
Driver and rider updates stream continuously, but matching decisions need a different consistency and latency profile.
Free Uber breakdown
How to answer Design Uber in a system design interview.
The center of gravity is dispatch and matching, not GPS maps. Strong answers explain how riders and drivers are matched under latency, geography, and supply-demand pressure.
Center of gravityDispatch before presentation.
MatchingLocation streamsSupply and demand
The pivot
Answer Uber like a marketplace, not a map app.
Optimize locally
Geography matters. Regional sharding and nearby candidate selection shape both latency and system structure.
Respect market pressure
Supply-demand imbalance, surge, and retry behavior change the problem from a simple nearest-driver lookup into a marketplace system.
Want the full version?
The paid Uber book goes deeper on dispatch and marketplace behavior.
The full breakdown covers rider-driver matching, location ingest, regional scaling, marketplace tradeoffs, and how to keep the answer focused.