title: Marathon vs Kubernetes vs Docker Swarm on DC/OS with Docker containers
body: <p>I'm looking for some pros and cons of whether to go with Marathon and Chronos, Docker Swarm or Kubernetes when running Docker containers on DC/OS. </p>
  
  <p>For example, when is it better to use Marathon/Chronos than Kubernetes and vice versa? </p>
  
  <p>Right now I'm mostly into experimenting but hopefully we'll start using one of these services in production after the summer. This may disqualify Docker Swarm since I'm not sure if it'll be production ready by then. </p>
  
  <p>What I like about Docker Swarm is that it's essentially just "Docker commands" and you don't have to learn something completely new. We're already using <code>docker-compose</code> and that will work out of the box with Docker Swarm (at least in theory) so that would be a big plus. My main concern with Docker Swarm is if it'll cover all use cases required to run a system in production.</p>