News for hackers. Stuff that matters.
Re:Practices for writing high-performance Go by rightbyte on Monday May 06, 2019 @02:38PM (#19842401)
Netflix OK but Uber? They did 4 billions rides in 2017. Thats naivly about 130 rides per second with nice parallelism due to locality of the physical rider. That's not an insane amount of data crunching.
Re:Practices for writing high-performance Go by Thaxll on Monday May 06, 2019 @03:31PM (#19842903)
You could say the same for Netflix, it's a giant CDN so why do they need 150k ec2 instances?

The problem they solve looks simple on the outside, the reality is different.

https://eng.uber.com/managing-data-workflows-at-scale/

Re:Practices for writing high-performance Go by devonkim on Monday May 06, 2019 @11:21PM (#19846195)
In my experience, most non-trivial sites are similar to icebergs of code - users might see 5% of the codepath in normal usage for what they want, but there's boatloads of OLAP, data analysis, instrumentation, error handling, and reporting being done on those transactions to help make that 5% both more profitable and reliable.
Re:Practices for writing high-performance Go by weberc2 on Tuesday May 07, 2019 @09:40AM (#19849181)
It’s not just rides, but also matching drivers with riders, geofence lookups, etc. it’s not a CRUD app.