HashiCorp Terraform vs. Salt Project

8 because it's currently best-in-class and is completely essential to use in contrast to not expressing your infrastructure as code. That said, new contenders are nipping at its heels, and I expect stronger tools to emerge in the coming years. Hopefully the Terraform team is able to keep pace.

Incentivized

Managing heterogeneous environments of large numbers of nodes, especially nodes which may need sudden changes (security updates, for instance), or frequent replacement, is a strength for Saltstack. Simplicity is not a strength for Saltstack. In a homogenous environment (all CentOS 7, for example, with no Debian or Windows) I might recommend using Ansible instead - it is less flexible and granular, but simpler to configure.

Incentivized

• Terraform is cloud agnostic. Just select the suitable provider for the cloud and it will do the job.
• Templating is possible to make the Terraform templates reusable.
• Variables can be created to make the templates generic so that it can be reused for different environments or resources.

Incentivized

• A superb remote execution framework! SaltStack allows us to easily program numerous functions on top of it. For example, we developed a fast parallel asynchronous deployment tool that handles all software deployment, including interdependent service management.
• Configuration management is now easy. We take advantage of this to automate (in tandem with AWS tools) the stand-up of all servers and services. It is also relatively easy to create new configuration management states for software not yet supported by the community (e.g. Grafana).
• Flexibility. Numerous small utilities have been built which simply wrap around SaltStack to allow tedious tasks to become easy.

Incentivized

• The errors generated by the plan and preview commands are pretty cryptic, it can be hard for newcomers to the scripting language to understand how to address problems.
• Access controls around workspaces is limited which makes it harder to secure reduce the scope of teams ability.
• Analytics around user usage, applies and plans would be helpful for managemenet.

Incentivized

• Managing network hardware should be more native and easy
• SaltStack should buffer jobs and, when a client returns, make sure it is executed proberly
• SaltStack should provide basic pillar and states structures to help get newbies started

Incentivized

I love Terraform and I think it has done some great things for people that are working to automate their provisioning processes and also for those that are in the process of moving to the cloud or managing cloud resources. There are some quirks to HCL that take a little bit of getting used to and give picking up Terraform a little bit of a learning curve, thus the rating

Incentivized

Terraform's performance is quite amazing when it comes to deployment of resources in AWS. Of course, the deployment times depend on various parameters like the number of resources to deploy and different regions to deploy. Terraform cannot control that. The only minor drawback probably shows up when a terraform job is terminated mid way. Then in many cases, time-consuming manual cleanup is required.

Incentivized

Terraform is community driven but does offer support for it's Enterprise product. When contacting the team at HashiCorp we have always gotten resolution to our issues. They have been very responsive in returning our calls and answering our questions as they come up. We are currently using the open source model.

Incentivized

We haven't had to spend a lot of time talking to support, and we've only had one issue, which, when dealing with other vendors is actually not that bad of an experience.

dbt was fine, but you end up with an extremely bloated repo/project. Often where all of the models are the same, named similarly, and generally just doesn't adhere to the concept of DRY coding. In Terraform we're able to template a lot of this work and dynamically generate assets based on variables instead.

Incentivized

I've used shell scripts over ssh, custom in-house deployment tools, Chef, and SaltStack. I've evaluated Ansible, but I was never happy with performance over SSH. Chef's loose configuration data model and lack of philosophy and conventions around use makes it difficult for a team to share responsibility for configuration code. Needing to use additional tools to do orchestration for cross-host/agent dependency relationships made me look for more. SaltStack, while not as mature when I first tried it, impressed me with its speed and elegant design

Incentivized

• Using code, we are able to build and deploy cloud resources faster and more consistently than producing the same resources in the console manually.
• For applications that share architectures, we can reuse code to expedite development. We can also do the same with modules that are shared across the organization.
• By defining all of our resources as code, we can deploy complete environments with "batteries included." For example, we can use code that spins up servers in a cloud provider and at the same time, creates monitors with in our monitoring provider. Likewise, when the servers are decommissioned, the monitors are decommed along with them. In the past, the creation and decom of the monitors would have been a disjointed, manual step. With Terraform we get it all with one "terraform apply."

Incentivized

• SaltStack has reduced the time it takes to deploy new machines for us 10-fold.
• It is much easier for us to maintain compliance with industry standards with SaltStack.
• No negative impacts!

Incentivized