Pallet vs Salt: What are the differences?
Pallet: Automates controlling and provisioning cloud server instances. DevOps for the JVM. The machines being managed require no special dependencies to be installed. As long as they have bash and ssh running, they can be used with pallet. Pallet has no central server to set up and maintain - it simply runs on demand. You can run it from anywhere, even over a remote REPL connection; 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..
Pallet and Salt belong to "Server Configuration and Automation" category of the tech stack.
Some of the features offered by Pallet are:
- Everything in Version Control
- Jar File Distribution of Crates
- Provisioning, Configuration and Administration
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.
Pallet and Salt are both open source tools. It seems that Salt with 10.1K GitHub stars and 4.59K forks on GitHub has more adoption than Pallet with 802 GitHub stars and 122 GitHub forks.
What is Pallet?
What is Salt?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Pallet?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Pallet?
What are the cons of using Salt?
What companies use Pallet?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Pallet?
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.
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.
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.