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

Consul

1.2K
1.5K
+ 1
213
Salt

418
448
+ 1
165
Add tool

Consul vs Salt: What are the differences?

What is Consul? A tool for service discovery, monitoring and configuration. Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.

What is Salt? 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..

Consul belongs to "Open Source Service Discovery" category of the tech stack, while Salt can be primarily classified under "Server Configuration and Automation".

Some of the features offered by Consul are:

  • Service Discovery - Consul makes it simple for services to register themselves and to discover other services via a DNS or HTTP interface. External services such as SaaS providers can be registered as well.
  • Health Checking - Health Checking enables Consul to quickly alert operators about any issues in a cluster. The integration with service discovery prevents routing traffic to unhealthy hosts and enables service level circuit breakers.
  • Key/Value Storage - A flexible key/value store enables storing dynamic configuration, feature flagging, coordination, leader election and more. The simple HTTP API makes it easy to use anywhere.

On the other hand, Salt provides the following key features:

  • Remote execution is the core function of Salt. Running pre-defined or arbitrary commands on remote hosts.
  • Salt modules are the core of remote execution. They provide functionality such as installing packages, restarting a service, running a remote command, transferring files, and infinitely more
  • Building on the remote execution core is a robust and flexible configuration management framework. Execution happens on the minions allowing effortless, simultaneous configuration of tens of thousands of hosts.

"Great service discovery infrastructure" is the top reason why over 49 developers like Consul, while over 41 developers mention "Flexible" as the leading cause for choosing Salt.

Consul and Salt are both open source tools. It seems that Consul with 16.2K GitHub stars and 2.82K forks on GitHub has more adoption than Salt with 10K GitHub stars and 4.58K GitHub forks.

According to the StackShare community, Consul has a broader approval, being mentioned in 131 company stacks & 52 developers stacks; compared to Salt, which is listed in 108 company stacks and 19 developer stacks.

Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Consul
Pros of Salt
  • 61
    Great service discovery infrastructure
  • 35
    Health checking
  • 29
    Distributed key-value store
  • 26
    Monitoring
  • 23
    High-availability
  • 12
    Web-UI
  • 10
    Token-based acls
  • 6
    Gossip clustering
  • 5
    Dns server
  • 4
    Not Java
  • 1
    Docker integration
  • 1
    Javascript
  • 47
    Flexible
  • 30
    Easy
  • 27
    Remote execution
  • 24
    Enormously flexible
  • 12
    Great plugin API
  • 10
    Python
  • 5
    Extensible
  • 3
    Scalable
  • 2
    nginx
  • 1
    Vagrant provisioner
  • 1
    HipChat
  • 1
    Best IaaC
  • 1
    Automatisation
  • 1
    Parallel Execution

Sign up to add or upvote prosMake informed product decisions

Cons of Consul
Cons of Salt
    Be the first to leave a con
    • 1
      Bloated
    • 1
      Dangerous
    • 1
      No immutable infrastructure

    Sign up to add or upvote consMake informed product decisions

    What is Consul?

    Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.

    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.

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

    What companies use Consul?
    What companies use Salt?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

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

    What tools integrate with Consul?
    What tools integrate with Salt?

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

    What are some alternatives to Consul and Salt?
    etcd
    etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines. It’s open-source and available on GitHub. etcd gracefully handles master elections during network partitions and will tolerate machine failure, including the master.
    Zookeeper
    A centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications.
    SkyDNS
    SkyDNS is a distributed service for announcement and discovery of services. It leverages Raft for high-availability and consensus, and utilizes DNS queries to discover available services. This is done by leveraging SRV records in DNS, with special meaning given to subdomains, priorities and weights (more info here: http://blog.gopheracademy.com/skydns).
    Ambassador
    Map services to arbitrary URLs in a single, declarative YAML file. Configure routes with CORS support, circuit breakers, timeouts, and more. Replace your Kubernetes ingress controller. Route gRPC, WebSockets, or HTTP.
    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