A challenge with Mesos is that Mesos was a piece of technology, a framework at most, instead of a product. When I was using Mesos, the selling point was flexible and efficient resource scheduling. Unfortunately, resource/machine efficiency alone does not sell well, as most of the companies and individuals have betters things to worry about, say, productivity.
> Unfortunately, resource/machine efficiency alone does not sell well...
Surprising because one of the driving forces behind accelerating adoption of on-demand IaaS and various PaaS like Serverless is that too many expensive server resources lay idle. According to James Hamilton, chief Data Center architect at AWS, server utilisation remains very low (10%–15%) despite servers being the most dominant cost of building and running a data center (which is to say, folks pay through their nose for servers yet those are under-utilized by a huge margin) [0]
I don't deny that. It's just that so many companies have so much inefficiency else where that addressing resource inefficiency has too low a marginal return.
One really does not want to saturate a fleet of servers to a point where random faults and broken SLOs are popping up all over the place. That’s first and foremost the main reason datacenter utilization is low.
>the selling point was flexible and efficient resource scheduling
There was a period when it wasn't clear that you didn't need both resource management and container orchestration. One of my colleagues was quite convinced at the time that we needed both Mesos and Kubernetes. If course, the market coalesced around Kubernetes which largely backfilled the missing capabilities.
