The framework-based scheduler architecture looked like an interesting concept at first sight. But its advantage (write your custom scheduling policy, along with

The framework-based scheduler architecture looked like an interesting concept at first sight. But its advantage (write your custom scheduling policy, along with gaining scalability) evidently wasn't that important to make up for the effort of actually having to write your own framework to run anything. (In this regard its a bit like object storage as a file system replacement narrative, which promises scalability, if you adapt your application). This seems to be true both for the Omega experiments at Google (which I assume still uses Borg), and for Mesos. In the end, Mesos always lacked even a minimal application deployment story. Marathon unfortunateley never got beyond being a shiny UI with a primitive application model and a hacky API. I think if Mesos(-sphere) had recognized that gap in time, and came up with a decent framework for application deployments, instead of telling everyone to write their own framework (in C++, against a hacky code base), Kubernetes might not have had a chance, or at least we would have two alternatives to chose from. Too bad.