Docker Swarm vs Apache Mesos

Need advice about which tool to choose?Ask the StackShare community!

Docker Swarm

+ 1
Apache Mesos

+ 1
Add tool

Docker Swarm vs Apache Mesos: What are the differences?

Docker Swarm: Native clustering for Docker. Turn a pool of Docker hosts into a single, virtual host. Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself; Apache Mesos: Develop and run resource-efficient distributed systems. Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.

Docker Swarm and Apache Mesos are primarily classified as "Container" and "Cluster Management" tools respectively.

"Docker friendly" is the primary reason why developers consider Docker Swarm over the competitors, whereas "Easy scaling" was stated as the key factor in picking Apache Mesos.

Docker Swarm is an open source tool with 5.63K GitHub stars and 1.11K GitHub forks. Here's a link to Docker Swarm's open source repository on GitHub.

According to the StackShare community, Docker Swarm has a broader approval, being mentioned in 83 company stacks & 38 developers stacks; compared to Apache Mesos, which is listed in 61 company stacks and 19 developer stacks.

Decisions about Docker Swarm and Apache Mesos
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 2.8M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More