When comparing Docker Compose vs Marathon on Apache Mesos, the Slant community recommends Docker Compose for most people. In the question“What are the best Docker orchestration tools?” Docker Compose is ranked 4th while Marathon on Apache Mesos is ranked 8th. The most important reason people chose Docker Compose is:
All that's needed to setup a multi-container application with Compose is a single file configuration file. Finally the application can be spun up with only a single command.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy setup
All that's needed to setup a multi-container application with Compose is a single file configuration file. Finally the application can be spun up with only a single command.
Pro Great for local development
Docker-compose isn't really meant (yet) for distributed deployment, but using it to deploy a website locally for testing is awesome. You could use it, with care (like handling faults), on a single server as well.
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
Cons
Con More geared towards development
No really made for production.
Con Not ready for production yet
While Compose is very good for staging servers, CI and development environments, it's still not ready for production and it's not recommended to be used in production yet.