4 ms·

I think there are tradeoffs, for example, they probably store the route, which is good (refunds for really terrible routes) but bad (tracking). That's quite a b

I think there are tradeoffs, for example, they probably store the route, which is good (refunds for really terrible routes) but bad (tracking). That's quite a bit of space, probably the big one. Rating and possibly comments, again could be pretty big. Multiple UUIDs or whatever (cust/driver IDs, CC txn IDs) will take up some space as well. 300B is probably a fair bit too low. That said, 100kB does seem high. 10kB or so would seem more appropriate, as a very rough ballpark.

rasen58 8y ago
They probably need to store a ton of things (like maps) that aren't data though, so probably not fair to say each ride is 100kb.
- Invictus0 8y ago
  Even if they have 20PB of maps, which is probably way too high, it's still 80kb.
NeedMoreTea 8y ago
Almost none of which they need to keep. Route for 30 days perhaps, start and end point for longer. I imagine most ratings are just that with no comments.
- MR4D 8y ago
  Routes determine pay to drivers, so they probably have to keep it much longer in case of a pay dispute.
  - p1necone 8y ago
    They could just give a digitally signed copy to the drivers and have the onus be on them to keep it.
btown 8y ago
Beyond the route itself, consider also: time spent in traffic (speed per geo-coordinate) for use in predicting surges, deviations between planned and taken routes, etc. The degree to which Uber has a pulse on urban traffic is fascinating and probably exceeds even city planners with access to ubiquitous traffic cameras.