Since publishing this blog a couple of days ago we have been fairly overwhelmed by the interest in it. I had some feedback from the man behind ConductR (Christopher Hunt from Typesafe) who put me straight on my comparison with Mesos and Marathon. It turns out that ConductR is not designed to replace Mesos, but rather to work with it as a highly available scheduler in the same way that Marathon does. The main differentiator for ConductR is that is aimed specifically at deploying and managing Typesafe Reactive Platform based apps and services.
In its current implementation, ConductR does not integrate with Mesos, instead it provisions its own basic resource provider on which to deploy applications. Christopher tells me that Mesos integration will be worked on during the second quarter of this year .... watch this space!
Having recently used Apache Mesos to deploy a Jenkins infrastructure as well as the Lift Application via Docker containers, I was very interested to see how Typesafe have interpereted this potentially game changing way of deploying applications.