HashiCorp Terraform Reviews and Ratings

Use Cases and Deployment Scope

We integrated HashiCorp Terraform for AWS configuration, such as VPC setup, subnets, routing, security groups, endpoints, etc.

Likelihood to Recommend

It is very useful for deploying a system or part of a system in the cloud. Such as AWS or Azure.You can also use it to manage the users and permissions of a database.You can have a version control by saving the IAC in a code repository.

Use Cases and Deployment Scope

There are two main problems the product solves for us. The first one is that it maintained our old EC2 image and the Matillion ETL instance it held; including backups, scheduled spin up times, snapshots etc. The second is to ingest raw data from our S3 data lake into Snowflake as raw data, and also to flatten it to tabular data.

Likelihood to Recommend

Anything that needs to be repeated en masse. Terraform is great at taking a template and have it be repeated across your estate. You can dynamically change the assets they're generating depending on certain variables. Which means though templated assets will all be similar, they're allowed to have unique properties about them. For example flattening JSON into tabular data and ensuring the flattening code is unique to the file's schema.

Use Cases and Deployment Scope

We use HashiCorp Terraform to deploy resources across various cloud providers as it supports maximum number of providers available in market. Best part of HashiCorp Terraform is terraform module as it provides feature of re usability of code. HashiCorp Terraform helps with Central code management for deployment of resources which is in line with organisational goal.

Likelihood to Recommend

One of the best IAC tool in market supporting wide variety of providers. Easy to understand code with really great documentations available across internet making its usage easy and feasible.

Use Cases and Deployment Scope

HashiCorp Terraform is an Infrastructure as Code (IaC) tool that allows us to describe resources that need to exist in our various cloud platforms, which provides a history and code review process.

Likelihood to Recommend

HashiCorp Terraform has a pretty difficult learning curve, but eventually the value is apparent once you get the grasp of it. We have lots of cloud resources, which are particularly well suited for an IaC platform. HashiCorp Terraform's excellent provider ecosystem allows us to implement large infrastructure changes with very few manual operations, and is critical to allowing us to bring up new environments quickly.

Use Cases and Deployment Scope

We are using HashiCorp Terraform CLI extensively in our platform for creating and managing AWS and Kubernetes resources. HashiCorp Terraform helps us to create multiple resources quickly within minutes. We are using it to differentiate configurations for different environments thereby helping us to manage our resources easily. Modules have also helped us in creating dynamic reusable templates for resource creations.

Likelihood to Recommend

Provisioning and managing cloud resources is great.

State management as well as reusable modules help greatly creating resources quickly.

onfiguration management like bootstraping a VM or running shell scripts commands can is quite tricky with HashiCorp Terraform.

Use Cases and Deployment Scope

I use HashiCorp Terraform to create development and production assets in AWS, Digital Ocean, and Linode environments.

Likelihood to Recommend

HashiCorp Terraform is very well suited for managing cloud-based assets for major cloud providers, including private cloud environments like Xen Orchestra and Proxmox for example. However some providers don't offer support for all of the features. It's not well suited at all for configuring cloud assets; in my opinion, tools like Ansible are much better suited for that.

Use Cases and Deployment Scope

We use Terraform to provision all our infrastructure in all major cloud providers (AWS,GCP,Azure), we have invested a lot to make our code repeatable and scalable as we need to support multiple accounts in each cloud provider.

Likelihood to Recommend

Terraform is the de-factor tool to provision infrastructure in an automated way, there are plenty of documentation and examples of people using the tool.

Terraform framework can be considered complicated to write efficient code, especially if you are doing some more complex use cases.

Creating efficient CICD pipelines is quiet challenge , I believe Terraform future will be replaced by Kubernetes operators.

Use Cases and Deployment Scope

It is used by our Cloud Services team. The business problems it addresses are automation and repeatability for things like multi environment deployments or for deploying duplicate architecture for each customer that a client may have. Our organization deals with many clients every day and some want their cloud environments to be architected in Terraform in order to easily deploy to new accounts, cloud providers, or even to other regions within an account.

Likelihood to Recommend

It is great for deploying relatively static architectures to new accounts or regions in the cloud. It can easily do other architectures but the best case is resources that are defined, the parameters can change but when you know what resources/services you need it's great. Less appropriate are cases where you will be dynamically changing resources or parameters on certain resources. It also might be difficult to write modules that use Lambda and things that have their own code base. This can be done but it's not as easy as simple tasks.

Use Cases and Deployment Scope

Terraform is currently being used to deploy infrastructure to GCP. We are mindful of the fact that some components might need other cloud providers and as Terraform is a cross-platform tool it is easier to manage the infrastructure with Terraform. It helps to iterate quickly.

Likelihood to Recommend

Terraform is amazing when you have a cloud environment. You can spend time designing the config files but you can save a lot of time when you have to deploy the same environment multiple times. For experimental cases, Terraform can be easily used to spin up environments and easily destroy them.

Use Cases and Deployment Scope

We use Terraform across multiple clients to track and maintain infrastructure as a code, Using Terraform help us to keep the tracking of the systems and improve the time to market, We use Terraform for deploy similar environments for development, staging and productions.

Likelihood to Recommend

When you need to deploy infrastructure and keep a track of your job. Use Terraform for keep your infrastructure make easy to find human errors and keep the history of changes in git or any repository if you use Terraform with your CICD tool you are in the state of the art in infrastructure management .