@rick.theengineer: Two drivers tapped ACCEPT on the same ride. Same block. Same moment. Milliseconds apart. One of them got it. Not because he was closer. Because his write hit the database first. And that little race is the most honest thing about Uber. Because Uber isn't really an app with a map — it's millions of moving phones being forced to agree, in real time, on one shared story of where everyone is. Think about what that actually takes. A million drivers reporting GPS every few seconds. You can't put that in a normal database — "find drivers within 3km" would scan every row while everyone's already moved. So there's a geospatial index carving the city into cells, answering in milliseconds. The car you watch gliding toward you? It's an animation between pings — a guess so smooth you never questioned it. The ETA isn't a number, it's a prediction engine chewing road networks, traffic, history, and live positions — and it changes mid-ride because the city changes mid-ride. The price isn't a price, it's a thermostat. Too many riders, too few cars, and the number climbs until drivers show up. Nobody sets it. The imbalance does. And when the payments service dies mid-trip — and it will — your car keeps driving, because the system was built assuming pieces of itself fail on a Friday night. One button. Six distributed-systems problems. A marketplace re-solving itself every second. I rebuilt the whole thing on one map in 2 minutes 36 seconds. The green line at the end is the entire business model. 🟢 #systemdesign #distributedsystems #uber #backendengineering #softwareengineering

RickTheEngineer

Open In TikTok:

Region: US

Monday 07 September 2026 14:25:02 GMT