Swarm vs. Fleet vs. Kubernetes vs. Mesos
Cloud Foundry has a scheduler called Diego[1], which is now in public beta on PWS. Because it's built for Cloud Foundry, you get the whole PaaS as well. No need to roll your own service injection, staging, logging, authentication and so on: it's already built and integrated.<p>For me, the cleverest part about Diego is that it turns placement into a distributed problem through an auctions mechanism. Other attempts at this focus on algorithmic approaches that assume perfect information. Diego instead asks cells to bid on incoming tasks and processes. The auction closes after a fixed time and the task or process is sent to the best bidder. This greatly reduces the need to have perfect central consistency in order to perform bin-packing optimisation -- in a real environment, that turns out to matter a lot.<p>Cloud Foundry is large and very featuresome, so for those who want a more approachable way to play with Diego, try Lattice[2].<p>Disclaimer: I work in Pivotal Labs, a division of Pivotal. Pivotal is the major donor of engineering effort to Cloud Foundry. I worked on the Buildpacks team and I've deployed commercial apps to PWS, so I'm obviously a one-eyed fan.<p>[1] <a href="https://github.com/cloudfoundry-incubator/diego-design-notes" rel="nofollow">https://github.com/cloudfoundry-incubator/diego-design-notes</a><p>[2] <a href="http://lattice.cf/" rel="nofollow">http://lattice.cf/</a>