When comparing Marathon on Apache Mesos vs OpenShift, the Slant community recommends OpenShift for most people. In the question“What are the best Docker orchestration tools?” OpenShift is ranked 7th while Marathon on Apache Mesos is ranked 8th. The most important reason people chose OpenShift is:
Learning to use OpenShift is pretty easy. Most environments can be set up in a few simple steps and for everything else the official documentation and third-party resources are extremely helpful.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Extremely fault-tolerant
Mesos handles (HA) master or agent failover; Marathon HA can survive scheduler failover; and Marathon automatically restarts failed tasks to maintain the desired number of task instances.
Pro Mesos is battle-tested at scale in production
Running all of Twitter, Apple's Siri, etc.
Pro Scalable to 10,000s of containers
Pro Free and Open Source
Pro Also supports non-Docker cgroups containers
Pro Small learning curve
Learning to use OpenShift is pretty easy. Most environments can be set up in a few simple steps and for everything else the official documentation and third-party resources are extremely helpful.
Pro Built-in continuous integration
Continuous integration is not only built-in OpenShift, it's actually a standard part the workflow.
Pro Can be used to introduce specialized tasks through the application hosted on it
Because of its high flexibility and customization power, OpenShift can be used to create specialized tasks for the application being hosted on it. For example, an entire array of dynos (also known as gears) can be dedicated to media transcoding in order to build a custom media converter infrastructure.
Cons
Con Official customer support is lacking
OpenShift seems to rely more on written documentation and on the community to solve any problem users may have. The forums and IRC channel are active and very helpful, but the official customer support could be better.