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

Docker Swarm

776
975
+ 1
282
Nomad

253
338
+ 1
32
Add tool

Docker Swarm vs Nomad: What are the differences?

Docker Swarm vs Nomad

Docker Swarm and Nomad are both container orchestration tools that help manage and automate the deployment, scaling, and management of containers. While they serve a similar purpose, there are key differences between the two tools.

  1. Architecture: Docker Swarm follows a swarm-mode architecture, where a swarm manager is responsible for managing and distributing workloads across a cluster of Docker nodes. On the other hand, Nomad follows a client-server architecture, where a Nomad server manages workloads across a cluster of Nomad clients.

  2. Supported Container Runtimes: Docker Swarm is tightly integrated with the Docker ecosystem and supports only Docker containers as the runtime environment. In contrast, Nomad supports multiple container runtimes such as Docker, rkt, and even non-containerized workloads like virtual machines.

  3. Scheduling Strategy: Docker Swarm uses a declarative scheduling strategy, where the user specifies the desired state of the swarm and Docker Swarm orchestrates the necessary actions to reach that state. Nomad, on the other hand, uses an imperative scheduling strategy, where the user directly schedules tasks and specifies the constraints and requirements for each task.

  4. Service Discovery: Docker Swarm integrates with Docker's built-in service discovery mechanism, which allows services to discover and communicate with each other using service names. Nomad, on the other hand, requires external service discovery mechanisms like Consul for service discovery and communication.

  5. Ecosystem Integration: Docker Swarm benefits from its tight integration with the Docker ecosystem, allowing seamless integration with other Docker tools and services. Nomad, while being independent of any specific ecosystem, provides a wide range of integrations with different tools and services, making it more flexible in terms of ecosystem choices.

  6. Scalability: Docker Swarm is well-suited for small to medium-sized deployments, offering simplicity and ease of use. Nomad, on the other hand, is designed for large-scale and complex deployments, providing more advanced features such as multi-region support, federated clusters, and hierarchical scheduling.

In summary, Docker Swarm provides a simple and tightly integrated orchestration solution specifically for Docker containers, while Nomad offers a more flexible and scalable approach with support for multiple container runtimes and a wide range of integrations.

Advice on Docker Swarm and Nomad

Hello, we have a bunch of local hosts (Linux and Windows) where Docker containers are running with bamboo agents on them. Currently, each container is installed as a system service. Each host is set up manually. I want to improve the system by adding some sort of orchestration software that should install, update and check for consistency in my docker containers. I don't need any clouds, all hosts are local. I'd prefer simple solutions. What orchestration system should I choose?

See more
Replies (1)
Mortie Torabi
Recommends
on
Docker SwarmDocker Swarm

If you just want the basic orchestration between a set of defined hosts, go with Docker Swarm. If you want more advanced orchestration + flexibility in terms of resource management and load balancing go with Kubernetes. In both cases, you can make it even more complex while making the whole architecture more understandable and replicable by using Terraform.

See more
Decisions about Docker Swarm and Nomad
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 8.9M 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 StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Docker Swarm
Pros of Nomad
  • 55
    Docker friendly
  • 46
    Easy to setup
  • 40
    Standard Docker API
  • 38
    Easy to use
  • 23
    Native
  • 22
    Free
  • 13
    Clustering made easy
  • 12
    Simple usage
  • 11
    Integral part of docker
  • 6
    Cross Platform
  • 5
    Labels and annotations
  • 5
    Performance
  • 3
    Easy Networking
  • 3
    Shallow learning curve
  • 7
    Built in Consul integration
  • 6
    Easy setup
  • 4
    Bult-in Vault integration
  • 3
    Built-in federation support
  • 2
    Self-healing
  • 2
    Autoscaling support
  • 1
    Bult-in Vault inegration
  • 1
    Stable
  • 1
    Simple
  • 1
    Nice ACL
  • 1
    Managable by terraform
  • 1
    Open source
  • 1
    Multiple workload support
  • 1
    Flexible

Sign up to add or upvote prosMake informed product decisions

Cons of Docker Swarm
Cons of Nomad
  • 9
    Low adoption
  • 3
    Easy to start with
  • 1
    HCL language for configuration, an unpopular DSL
  • 1
    Small comunity

Sign up to add or upvote consMake informed product decisions

What companies use Docker Swarm?
What companies use Nomad?
See which teams inside your own company are using Docker Swarm or Nomad.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Docker Swarm?
What tools integrate with Nomad?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Docker Swarm and Nomad?
Docker Compose
With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.
Rancher
Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.
Ansible
Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.
Apache Mesos
Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.
CoreOS
It is designed for security, consistency, and reliability. Instead of installing packages via yum or apt, it uses Linux containers to manage your services at a higher level of abstraction. A single service's code and all dependencies are packaged within a container that can be run on one or many machines.
See all alternatives