How Uber Uses Your Phone as a Backup Data Center
summary
Claim: Uber restores live trip state from driver phones so city failovers don’t drop trips. Implementation: a replication service immediately queues updates, a separate messaging channel pushes an encrypted key-value blob to phones that support get set delete list with set-once keys and versioning via a modified vector clock. Completed trips store compact tombstones so weeks of history fits. Validation: an hourly collector performs shadow restoration into the backup datacenter to measure restoration success and load readiness.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:33Life of an Uber Trip
- 2:05Death of an Uber Trip
- 2:27Saving Uber Trips
- 6:06Keep The Protocol Simple
- 7:55Designing the perfect solution
- 9:39Non-blocking and eventually consistent
- 16:0099.99% reliability
related talks
41mHow Uber Audits Real time Infrastructure of Trillion+ Messages
38mEvolution of Uber's Search Platform
29mCulturing Resiliency with Data: A Taxonomy of Outages
43mHow WhatsApp moved 1.5B users across data centers
41mDesigning Architecture for a Fault-Tolerant Taxi Service
52mTaking Storage for a Ride
32mHow Uber Optimize Marketplaces with Ray
38m"Explorations in Cooperative, Distributed Systems with Uber's Ringpop"