3 ms·
Can't speak for OP, but I'd imagine most of the data in the system is metadata - i.e. very tiny. Sure they're moving a lot of packets, but an entire ride's dat
by theincredulousk 7y ago
Can't speak for OP, but I'd imagine most of the data in the system is metadata - i.e. very tiny. Sure they're moving a lot of packets, but an entire ride's data could probably fit in 100KB. If they have a million drivers active, what data do they actually need on them? Profile, GPS location, type? Few KB. Keeping the log of all rides probably takes up the most, but still, relatively small. In any case they essentially deal with small, highly compressible metadata.
Think of that vs. a company like Instragram where people are uploading probably terabytes of media content every day, and they have to maintain/host all that content to be served on-demand basically forever. This is probably a low-key reason for pushing "stories" - they get a reprieve by only having to store that for 24 hours. In any case, you're looking at orders of magnitude larger data usage in all aspects.
- spookthesunset 7y agoUber eats, for example, gives a guess of when your order arrives based on past data. Uber gives estimates of when your ride will show up. They do lots of stuff in fairly real time with that data and a lot of it is probably compute intense. Not at all comparable to Instagram.
- tln 7y agoOr YouTube, with 1000s of hours of video uploaded per minute. FWIW an Instagram pic, 1080x1080 is around 100kb. Uber has to do a lot more processing on it's data. I'm sure there are real challenges and the OSS projects from Uber I've seen/remembered on HN seem to be the type one builds because existing tools don't solve the problem well enough for their cases.
- erghoe 7y agoFWIW, Instagram stores Stories, privately to the user, in its "Archive" feature indefinitely. https://instagram-press.com/blog/2017/12/05/introducing-stories-highlights-and-stories-archive/ https://instagram-press.com/blog/2017/12/05/introducing-stor...