Earlier quoted context omitted.
> Exactly, and you can't solve a problem by making it more complex. Sure you can. A resource scheduler is more complex than not having one, but it solves the single-point-of-failure problem and the bin-packing CPU+memory problem. A more complex infrastructure means you can have dumber apps. And there are lots of areas where this is true: TCP is a complex protocol which makes it easier to build reliable communication,…
> A resource scheduler is more complex than not having one, but it solves the single-point-of-failure problem and the bin-packing CPU+memory problem. And yet various FAANGs choose not to use a smart scheduler, because it does not improve efficiency and reliability enough to justify its complexity and scales poorly.
Netflix uses Titus and Mesos [2].
I'm not sure what Amazon uses, but I'm sure they have some sort of system to do this. They offer plenty of managed solutions for customers (including EKS).
Apple's more of a product company, but they seem to use Kubernetes for some things [3].
And finally facebook apparently has something called Tupperware [4].
So all the FAANGs use something like Kubernetes to manage infrastructure.
[1] https://en.wikipedia.org/wiki/Borg_(cluster_manager) [2] https://queue.acm.org/detail.cfm?id=3158370 [3] https://jobs.apple.com/en-us/details/200120515/virtualized-c... [4] https://www.slideshare.net/Docker/aravindnarayanan-facebook1...