Get Advice Icon

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

Docker Swarm
Docker Swarm

427
412
+ 1
207
Salt
Salt

294
206
+ 1
136
Add tool

Docker Swarm vs Salt: What are the differences?

Developers describe Docker Swarm as "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. On the other hand, Salt is detailed as "Fast, scalable and flexible software for data center automation". Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more..

Docker Swarm and Salt are primarily classified as "Container" and "Server Configuration and Automation" tools respectively.

"Docker friendly" is the primary reason why developers consider Docker Swarm over the competitors, whereas "Flexible" was stated as the key factor in picking Salt.

Docker Swarm and Salt are both open source tools. Salt with 10.1K GitHub stars and 4.59K forks on GitHub appears to be more popular than Docker Swarm with 5.63K GitHub stars and 1.11K GitHub forks.

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

What is Docker Swarm?

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.

What is Salt?

Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.
Get Advice Icon

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

Why do developers choose Docker Swarm?
Why do developers choose Salt?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use Docker Swarm?
    What companies use Salt?

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

    What tools integrate with Docker Swarm?
    What tools integrate with Salt?

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

    What are some alternatives to Docker Swarm and Salt?
    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.
    Kubernetes
    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
    See all alternatives
    Decisions about Docker Swarm and Salt
    StackShare Editors
    StackShare Editors
    Ansible
    Ansible
    Puppet Labs
    Puppet Labs
    Salt
    Salt

    By 2014, the DevOps team at Lyft decided to port their infrastructure code from Puppet to Salt. At that point, the Puppet code based included around "10,000 lines of spaghetti-code,” which was unfamiliar and challenging to the relatively new members of the DevOps team.

    “The DevOps team felt that the Puppet infrastructure was too difficult to pick up quickly and would be impossible to introduce to [their] developers as the tool they’d use to manage their own services.”

    To determine a path forward, the team assessed both Ansible and Salt, exploring four key areas: simplicity/ease of use, maturity, performance, and community.

    They found that “Salt’s execution and state module support is more mature than Ansible’s, overall,” and that “Salt was faster than Ansible for state/playbook runs.” And while both have high levels of community support, Salt exceeded expectations in terms of friendless and responsiveness to opened issues.

    See more
    Yshay Yaacobi
    Yshay Yaacobi
    Software Engineer · | 27 upvotes · 277.5K views
    atSolutoSoluto
    Docker Swarm
    Docker Swarm
    Kubernetes
    Kubernetes
    Visual Studio Code
    Visual Studio Code
    Go
    Go
    TypeScript
    TypeScript
    JavaScript
    JavaScript
    C#
    C#
    F#
    F#
    .NET
    .NET

    Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

    Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

    After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

    See more
    Interest over time
    Reviews of Docker Swarm and Salt
    Review ofSaltSalt

    For automating deployment or system admin tasks, Shell/Perl are more than enough. Specially Perl one liners, that I use heavily, even to make changes in xml files. But quite often the need is to just check the state of system and run scripts without fear. Thats where I actually needed some scripting language with "state mechanism" associated with it. Salt provided me above similar kind of experience. I tested salt first on a small scenario. Installation of 60 RPMS on a machine. I was pleased that I could achieve that in around 25 lines of code using salt. And eventually I was also able to keep data and code separate. This was another plus point. henceforth I was able to use salt to deploy a large potion Datacenter (apps deployment). I am still working towards orchestration and finding it quite promising. The use of pure python whenever needed to deal with more complex scenario is awesome.

    How developers use Docker Swarm and Salt
    Avatar of Refractal
    Refractal uses SaltSalt

    When it comes to provisioning tens to hundreds of servers, you need a tool that can handle the load, as well as being extremely customisable. Fortunately, Salt has held that gauntlet for us consistently through any kind of issue you can throw at it.

    Avatar of FAELIX
    FAELIX uses SaltSalt

    We've built something using SaltStack and Debian Linux to help us deploy and administer at scale the servers we provide for our part- and fully-managed hosting customers.

    Avatar of Runbook
    Runbook uses SaltSalt

    Everything is deployed via Salt. From configurations to Docker container builds.

    Avatar of Aspire
    Aspire uses SaltSalt

    Simple configuration of vagrant for development environments.

    Avatar of SAP Hybris
    SAP Hybris uses SaltSalt

    configuration manager and orchestrator for deployment

    How much does Docker Swarm cost?
    How much does Salt cost?
    Pricing unavailable
    Pricing unavailable
    News about Salt
    More news