We use HashiCorp Terraform for Infrastructure as Code. It automates the deployment of infrastructure within the Azure platform. Terraform can manage almost all aspects of infrastructure provisioning. If there are tasks that Terraform cannot perform directly, you can use the Azure CLI or other tools and call them from within Terraform scripts.
HashiCorp [Private Offer Only]
Carahsoft Technology Corp.External reviews
9 reviews
from
External reviews are not included in the AWS star rating for the product.
Has extensive integrations across various platforms
What is our primary use case?
How has it helped my organization?
Terraform has extensive integrations across various platforms. It includes modules that enhance functionality and support for secure practices, such as Terraform Sentinel, which offers code analysis capabilities. Security logging and backend security are crucial, particularly regarding protecting sensitive information stored in the backend. Ensuring private endpoint usage is pivotal to safeguarding against potential vulnerabilities.
What is most valuable?
Terraform's strength lies in its modularity and the ability to use variables. You can organize your code within local and remote repositories, making it highly modular. This modularity allows you to call specific components as needed. Additionally, Terraform can toggle certain functionalities on or off through feature flags, a unique and powerful feature.
What needs improvement?
Terraform should monitor the backend storage more closely. You can handle it within Azure, but HashiCorp should release a dedicated tool to protect those secrets and ensure they're fully encrypted but this functionality is on its way for Terraform. They do have functionality that encrypts secrets and rotates which is great just like what Microsoft have and should be used in the wider community to safeguard public cloud systems
For how long have I used the solution?
I have been using HashiCorp Terraform for five years.
What do I think about the stability of the solution?
The product is quite stable. You may not notice the updates, but you do see frequent changes in revisions because they've stabilized the platform. They've also introduced significant new versions and providers that work hand in hand with it. I don't encounter many errors that I can't fix straightforwardly. As an engineer, you receive error messages if you misconfigure things, and it informs you about that.
I rate the solution’s stability an eight out of ten.
What do I think about the scalability of the solution?
The solution can scale to any size. It is suitable for SMEs.
I rate the solution’s scalability an eight out of ten.
Which solution did I use previously and why did I switch?
Arm templates where difficult to managed initially and took a while to manage in nested calls and nested templates
How was the initial setup?
The integration is straightforward. Simply download the binary, test it accordingly, and authenticate via Azure CLI. I've used the standard binary because it's free and widely adopted for technical infrastructure as code.
The initial setup is very straightforward. I set up a Python environment, brought in Terraform, and utilized it with YAML. Everything has to be securely done. You have to set up some pieces on the backend. It's straightforward to deploy: get the binary, set it up on the build agent, and configure the settings the way you need.
What about the implementation team?
Inhouse Initially but I have learnt form other teams and vendors as all teams structure their code differently with best practices
What's my experience with pricing, setup cost, and licensing?
We are using the free version of the solution.
Which other solutions did I evaluate?
Arm Templates and PowerShell Azure initially Pulumi (early days)
What other advice do I have?
I've been working with HashiCorp Terraform recently and have deployed environments with it.OpenAI has released GPT Terraform, which Microsoft is heavily investing in. Generic modules are available for deployment. Azure AI Portal and AI Studio are useful tools for creating models. It's straightforward to perform service training and update models for input-output data.
HashiCorp Terraform has made handling modules and variables more secure. They've integrated key vaults to ensure secrets and backend storage are protected. Accessing the backend storage could potentially leak sensitive information if not properly encrypted.
I'm using GitHub Actions and Azure DevOps. Additionally, I'm exploring an older system within the team that will be set up to support.
If the setup is built on old infrastructure, the backend of Terraform works and stores. Vagrant works differently where it doesn't need to check with the infrastructure to see what's there or updated. You get an API call for deployment.
Overall, I rate the solution as eight out of ten.
Manages infrastructure and is responsible for creating and managing infrastructure components
What is our primary use case?
HashiCorp Terraform is primarily used to manage infrastructure. It is responsible for creating and managing infrastructure components. For example, when we initially designed the infrastructure for this project, we started by designing the VPC. We decided to use a specific region-based VPC. We specified the number of public and private subnets, as well as setting up Internet gateways and NAT gateways, all using Terraform. Once the infrastructure was set up, we deployed our resources, such as ECS containers, ECS tasks, and RDS databases, in private subnets, all properly managed by Terraform.
However, we use GitHub Actions for CI/CD pipeline purposes. While Terraform handles the infrastructure management, GitHub Actions manages the CI/CD pipeline for our ECS clusters. In my previous project, we used Jenkins, but in this project, we use GitHub Actions for deployment, testing, and other pipeline tasks.
What is most valuable?
Terraform is that it is an open-source tool that gives us great flexibility. Using the Terraform HCL, we are not restricted to a single cloud provider. If my client asks me to deploy the same infrastructure on Azure or GCP, I can use the same code with minor modifications to account for the different providers. This means we are not limited to a specific cloud.
Unlike AWS CloudFormation, which is limited to AWS, Terraform allows us to use a single platform and tool to deploy infrastructure across multiple clouds or on-premises environments. This makes it very easy for us to manage our infrastructure without switching tools or languages. While CloudFormation uses JSON or YAML, HCL is well-documented and user-friendly. It has documentation provided for HCL, which covers almost everything we need to know to use it effectively across different environments.
What needs improvement?
Terraform does not provide an automatic feature to convert infrastructure code from one cloud platform to another. For example, if I am creating infrastructure on AWS using a VPC and I want to deploy a similar infrastructure on another cloud platform like GCP or Azure, I need to manually rewrite the code to accommodate the different services and resources specific to each cloud provider.
Terraform is very helpful for managing infrastructure across multiple clouds, but it requires using different providers and adapting the code to match the services offered by each cloud platform. An automatic feature to convert Terraform code for use on different platforms would be beneficial, as it would simplify the process for developers. However, such a feature does not exist now, so developers must manually convert the code when switching between cloud providers.
What do I think about the scalability of the solution?
50-60 percent of clients will use Terraform if we use ten projects with DevOps resources.
Most new clients lack experience or knowledge about Terraform or other IaC tools. They manage their enterprise infrastructure manually. However, clients with experience and knowledge in IaC services typically prefer using Terraform. Most clients without this experience do not use Terraform or any IaC tools, opting instead to manage everything manually.
How are customer service and support?
I was facing some issues, but I didn't approach them because I just read the Terraform documentation and the community groups to find a solution.
How was the initial setup?
Installing Terraform is straightforward on any Linux or Windows-based operating system. However, managing different versions of Terraform can present some challenges. If you're using an older version and need to upgrade to the latest version, you might encounter some issues, such as syntax errors or changes in required formatting. It has built-in modules available in the Terraform documentation; managing upgrades and ensuring compatibility with your existing code can be more complex. Creating custom modules requires some initial effort, but they can be reused as needed.
What's my experience with pricing, setup cost, and licensing?
Terraform is free to use. You don't need to pay for Terraform itself because it's open-source. You need to write the code; the actual cost comes from the resources you create on your cloud provider. The code itself is free, and you can write your modules. Most companies prefer to write their modules instead of using the built-in ones provided by AWS, Google, or Azure. A module is a one-time effort to create, and you can reuse these modules to create multiple resources in your cloud environment.
What other advice do I have?
You must use Terraform when your client plans to scale the infrastructure or replicate it in another region in the future. Terraform is beneficial because once you write the code, it becomes easy to create similar resources in other availability zones or regions.
For small web applications with limited resources, Terraform might not be necessary. However, if your client anticipates major changes or deployments and is thinking about scaling the infrastructure, Terraform is a must. It makes management easier.
Another significant benefit of Terraform or any other IaC tool is that organizations are not reliant on individual resources. For instance, if you lead a DevOps department, you won't depend on a specific DevOps engineer to create the infrastructure. Managing resources through code or cloud automation simplifies scaling the infrastructure without deep knowledge of the underlying code.
For example, if you need to create another EC2 instance for your application, applying small changes to your Terraform code is straightforward. Since your infrastructure code is stored in version control systems like GitHub or Bitbucket, it isn't dependent on individual systems. You can pull the code from GitHub, make changes, and apply them regardless of where you are, which adds to the convenience.
I prefer Terraform because of the documentation and open-source community.
As someone who provides training on various tools, including Terraform, I've observed that many students lack experience with It. One of the main prerequisites for learning Terraform is knowledge of AWS or any other cloud platform on which you want to create your resources. If you know how to create resources manually, it will be much easier to convert them into IaC.
Overall, I rate the solution a seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Has an easy setup phase and offers an open-source version to users
What is our primary use case?
I use the solution in my company to create services over cloud platforms. I have used HashiCorp Terraform for GCP, Azure, and AWS to create resources. With HashiCorp Terraform, it is easy to manage resources in a single file.
What is most valuable?
The most valuable feature of the solution stems from the modules it offers. One can find Terraform modules via Google.
What needs improvement?
The versions of Terraform providers are an area of concern where improvements are required. If a person wants to use the modules created by someone else a few years ago, then there is a need to change all the resources or use the version of the product in which the modules were created. The modules are suitable only for the particular provider version on which they were created. The product should be made more dynamic in nature.
For how long have I used the solution?
I have been using HashiCorp Terraform for five years. I am a customer of the product.
What do I think about the stability of the solution?
It is a stable solution. Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution a nine out of ten.
Which solution did I use previously and why did I switch?
I have experience with AWS CloudFormation.
How was the initial setup?
The product's initial setup phase was easy.
The solution is deployed on the cloud or an on-premises model.
The solution can be deployed in five people if the person is an expert in the use of searching for information on Google.
What's my experience with pricing, setup cost, and licensing?
It is an open-source product.
What other advice do I have?
A scenario where the product improved our company's deployment process stems from an incident where I was working for one of our organization's clients where we had to set up a complete application offering for them. There were no disaster recovery options available due to cost-related issues. Whenever there is any disaster, my company pops up a particular DR environment, after which the application can go live from such an environment. My company lost all the resources due to the lack of a DR environment. Using HashiCorp Terraform, my company created state files in which we changed the reasons and created a complete infrastructure in a single go. With the help of HashiCorp Terraform, it took my company only 13 or 14 minutes to ensure that the application went live from our end.
The product's state file management feature greatly enhances our company's infrastructure. In our company, it is great that the tool allows us to manage the state file over the cloud or any bucket offered under Azure or Amazon S3's services, and the fact that we can directly fetch the data with the ID from the state file, making it an area that becomes easy to manage for users. For reusability, it is easy.
I recommend the product to those who plan to use it. Whenever people want to create or publish a module, we need to specify the version for HashiCorp Terraform and providers. Whenever someone wants to use a modular after a few years since it was created, such a person will be able to easily understand the version of HashiCorp Terraform to be deployed since searching for the version can be time-consuming.
I rate the overall tool a nine out of ten.
Offers flexibility, clear documentation, and the ability to handle diverse use cases
What is our primary use case?
What is most valuable?
The most valuable features of Terraform are leveraging public modules for EKS, KMS, and ECR. This allows us to set up infrastructure efficiently by utilizing pre-built configurations. We can manage EKS either through the EKS Manager group or directly with specific variables. This flexibility is crucial as it doesn't require building privileges.
What needs improvement?
Some areas where Terraform could improve would be challenges in managing sensitive information, especially when dealing with secret files or credentials. There have been issues related to storage and maintenance of these files, particularly when using AWS. Simplifying the process of handling secrets and improving the overall management of sensitive data could enhance Terraform's usability. One suggestion for Terraform improvement could be enhanced remote functionality. It would be beneficial if, for example, I could remotely check the status and perform tasks directly on AWS without needing a full analysis of all tasks locally.
For how long have I used the solution?
I have been working with Terraform for two years.
What do I think about the stability of the solution?
I would rate the stability of Terraform as a seven out of ten. While generally stable, there is room for improvement to minimize challenges and provide a smoother experience for users.
What do I think about the scalability of the solution?
Terraform is highly scalable. I would rate the scalability as a nine out of ten. Ten people use it at our company.
How was the initial setup?
The initial setup was very simple and quick. It takes about two minutes to install everything.
Which other solutions did I evaluate?
When comparing Terraform with other infrastructure automation tools, I often consider AWS CloudFormation. However, I prefer Terraform for its versatility and ease of use. The abundance of modules, well-documented features, and direct integration with AWS makes it my go-to choice. Its flexibility, clear documentation, and ability to handle diverse use cases, from managing directories on GitHub to updating Linux machines, contribute to its efficiency and simplicity.
What other advice do I have?
Overall, I would rate Terraform as an eight out of ten.
Works like a coding language
What is our primary use case?
We use Terraform for many different use cases. The primary one is ensuring that the security policy is automatically applied to all of the resources within a cloud environment. Another one would be creating and dismantling all sorts of test labs, as well as creating a development environment. We found a way to automatically create a development environment only for the time we need. We develop the infrastructure and cloud-related tasks.
What is most valuable?
The most valuable feature of Terraform is the ability to use it as a coding language because it works in a way that's similar to other coding languages. They are able to create classes, loops, etc. If you're familiar with coding, you will not have issues with learning to use Terraform.
What needs improvement?
One thing where Terraform could use improvement would be the types of resources it supports. With cloud providers always adding new resource types, there are certain resources that Terraform does not support. It would be great if it could support those resources as well.
For how long have I used the solution?
I have been using Terraform for three years.
What do I think about the stability of the solution?
I give it a ten out of ten for stability.
What do I think about the scalability of the solution?
Terraform is very scalable. A ten out of ten. About four or five DevOps engineers use Terraform at my company.
We plan to increase its usage. I come from the security world and Terraform is very useful in ensuring that off of the resources within a cloud environment are deployed in a unified way. If you build the Terraform script once and you ask to create a different type of resource, instead of going into the Azure or AWS console and creating the resource from scratch, they use your Terraform script and ensure that all of the secured measures you've deemed necessary are built into that deployment.
How was the initial setup?
I would rate the easiness of the setup a nine out of ten. It takes a maximum of 15 minutes to deploy it, but you need to write the script you want to run first, which takes more time since writing it depends on what you want to do.
I deployed it myself, but Terraform has some great, open people who contributed to the project. Specifically, the cloud part of the project had a lot of valuable contributions and made the deployment easy.
What's my experience with pricing, setup cost, and licensing?
I am currently using the free version of Terraform.
What other advice do I have?
My advice to new users would be to understand that Terraform works like a coding language, so you need to understand how it loops over objects in the same way that coding language loops over. objects You should turn Terraform terms into classic coding terms.
Overall, I rate it a ten out of ten.
The solution provides a reliable deployment approach that puts it ahead of its competition
What is our primary use case?
The solution is a success code. We use open-source software.
What is most valuable?
The first thing I like about the solution is that it keeps a version of your infrastructure. And you always have, for example, the bill of materials with what it produces in terms of YAML files that you can manipulate and understand exactly what infrastructure you deploy, what is active, and what is not. We use it with the Amazon database, where the solution does not deploy the second time if somebody triggers a build or deployment. Apart from those features, the fact that you have your infrastructure on code is tremendous.
What needs improvement?
It would be nice if they could put our infrastructure on graphics or at least provide a map of our infrastructure, especially with links, to see what it looks like graphically. That way, we could understand the relationship between all the machines. That helps with redundancy purposes, where, for example, if we need to create redundancies to create high availability for some services, we could look at the map directly.
For how long have I used the solution?
I've worked with the solution for three or four years.
What do I think about the stability of the solution?
The solution works very well every time. It calls APIs from Amazon, so it's always up to date. I rate the solution's stability a nine out of ten because we never had a problem.
What do I think about the scalability of the solution?
I rate the solution's scalability an eight out of ten. It's pretty scalable on the Amazon cloud. We have around three or four users on the solution.
How are customer service and support?
HashiCorp's technical support is very good. They know what they're talking about.
How was the initial setup?
The initial setup is really simple. We just created YAML files with what we needed, and somebody deployed machines and load balancers. It's just a binary we needed to place anywhere.
We deployed the solution on Amazon's cloud. For the AKS cluster, we just launched Terraform, which region and which kinds of machines we wanted to install.
Which other solutions did I evaluate?
Terraform's philosophy is different, but Ansible is a similar product. It's not the same, though you can also deploy virtual machines, for example. However, I would not use Ansible because it does not have the same features as Terraform when it comes to history. Terraform pulls the API first to understand what you have from your schema and compare it with your existing infrastructure.
Ansible would not do that. It would just execute the code and deploy without knowing what it does.
What other advice do I have?
We don't use Terraform in a very fancy way. The solution did not have a difficult use case, nor did we go into a specific feature of Terraform that we tested very thoroughly. We used it in a basic way, simply trying not to run the same script twice or by two people simultaneously.
I rate HashiCorp Terraform a nine out of ten and recommend it to everyone.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Setting up Terraform is easy and provides flexibility in how you can use it
What is our primary use case?
We use this solution to make our migration plan and utilize the images of Azure, GCP, and EC2 instances for our infrastructure. We have basic applications that the bank requires, so we use Terraform to expedite the initial infrastructure preparation. We also created a couple of common modules that we can use in production, development, and test environments.
What is most valuable?
The environment is very good. That's awesome.
What needs improvement?
At present, they only support around 300 applications and services from different clouds. They should aim to support more than a thousand to stay ahead of their competitors.
The product can integrate and utilize more services from different competitors. Currently, their commands are quite similar to Kubernetes, which we use in our CI/CD pipeline. Also, they should consider incorporating Windows command line, like PowerShell.
Moreover, they should involve more technologies instead of just being providers for managing infrastructure; they could become active players in the field.
For how long have I used the solution?
I have been using this solution for one and a half years.
What do I think about the stability of the solution?
The solution is pretty stable. I would rate the stability a nine out of ten.
What do I think about the scalability of the solution?
I would rate the scalability an eight out of ten.
How was the initial setup?
The initial setup is easy. You just need to provide the description and the value for that particular setup. You don't have to learn or by heart remember all those commands. It's really easy. For example, if I want to create a DNS entry, I can use the data as well as resource parameters for the same.
So, that sort of flexibility allows me to use it differently, depending on my needs. When I use it as data, I can redirect my DNS to somewhere else because I'm using GCP as my service provider for my on-premise website. So, I route the incoming requests via GCP using load balancers. I use data as a resource for this. When I'm using Azure DNS, I utilize a resource command for the same in the data.
We have deployed it both on cloud and on-premises.
What's my experience with pricing, setup cost, and licensing?
The solution is comparatively cheaper than the others.
What other advice do I have?
If you want to stay on top, you should be involved not only in maintaining your current infrastructure but also in adapting to changes. For example, if HashiCorp incorporates certain Linux commands, it will attract more people from the infrastructure field, especially those with a Linux background.
Overall, I would rate the solution a ten out of ten.
An affordable and scalable solution that provides a self-service infrastructure
What is our primary use case?
I am using the solution on AWS to scale our operations using Infrastructure as Code.
How has it helped my organization?
Terraform is the most useful product for creating Infrastructure as Code. It has a lot of consistency, and we can control it in code. It provides a self-service infrastructure.
What is most valuable?
The solution helps us save a lot of costs. The product’s integrations help us a lot.
What needs improvement?
The product must improve DevOps features.
For how long have I used the solution?
I have been using the solution for about two years.
What do I think about the stability of the solution?
I never had any stability issues. I rate the stability a ten out of ten.
What do I think about the scalability of the solution?
It is easy to scale the product. I rate the scalability a ten out of ten.
Which solution did I use previously and why did I switch?
We use other solutions for security in DevOps.
How was the initial setup?
The solution is deployed on the cloud. It is easy to deploy the solution. The documentation helps us a lot.
What was our ROI?
The tool has a lot of value. It pays for itself. We save a lot of time using the automation.
What's my experience with pricing, setup cost, and licensing?
The solution is fairly priced.
What other advice do I have?
We're still learning how to use DevOps with our SOC. We need to improve our use cases. The tool is helpful for us to keep the same standards throughout the cloud. Currently, I'm only using AWS. I'm planning to use Azure in a few months. I would advise people to start using the solution. It is a cheap tool and saves us a lot of work. Overall, I rate the product a ten out of ten.
A reasonably stable tool that offers high compatibility with multiple cloud providers
What is our primary use case?
My company uses HashiCorp Terraform for cloud infrastructure provisioning. HashiCorp Terraform is the only IaC tool we use in our company.
What is most valuable?
The most valuable features of the solution are its simplicity of HCL language, its compatibility with multiple cloud providers, and its modules like the open source modules available, especially considering the fact that I work mainly on AWS. I believe that HashiCorp Terraform is one of the best products available in the market for my company's use cases. HashiCorp Terraform is also a feasible solution in terms of its availability of cloud resources.
What needs improvement?
I know a UI tool is available in the licensed version of HashiCorp Terraform. From a user's perspective, it would be great if a UI tool is made available in the open source version as well, but I don't think it may be introduced because of the high costs for it announced by HashiCorp in its licensed version.
HashiCorp Terraform can improve backward compatibility. From users' perspective, migration from one version to another is okay. The migration from an older version to a newer version is a big challenge in HashiCorp Terraform. We tried to fix the migration issues multiple times at our end and saw that some will not be compatible sometimes while, at times, certain aspects will be compatible with the new version.
For how long have I used the solution?
I have been using HashiCorp Terraform for four years. I use HashiCorp Terraform v0.12 or v0.13. I use the open-source version of the tool for my company's internal usage.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution a nine out of ten.
My organization has around 30 to 40 users of the solution.
How was the initial setup?
The simplicity or complexity of the initial setup depends on the number of accounts involved in the setup phase on the cloud, along with the resources to be managed. Based on my experience, one won't find HashiCorp Terraform's setup difficult if the configuration and management are in place.
The solution is deployed on the public cloud. I know people who use the solution on private and hybrid clouds.
What other advice do I have?
For those users with their infrastructure on the cloud, I would say that Terraform is a tool they can use immediately, even though other tools like Ansible are in the market. At some point, one may feel that Ansible lacks efficiency in a cloud infrastructure, which is a difficulty one may face when using Terraform in a bigger infrastructure. I would say that the combination of Ansible and Terraform is the best.
When following complex methods, Ansible is the best option. If you do too much configuration on the standalone file, then if not today, then tomorrow you might be stranded in a situation where you might not be able to edit or modify the configuration, especially when some improvements related to certain features have to be included in the product or your product's existing portal. It will be very tough to deal with, especially when it will be a single file with thousands of clients, making it a tough job to search. So you need to make sure that code reusability is properly using in your terraform code base.
I rate HashiCorp Terraform a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
An easy-to-deploy solution that can be used for Infrastructure as Code (IaC)
What is our primary use case?
We use HashiCorp Terraform for Infrastructure as Code (IaC).
What is most valuable?
The most valuable feature of HashiCorp Terraform is the custom modules. The custom modules are built for each piece, like network and security, based on how the customers are. Then, we can tie them together, centralize them easily, and build them.
What needs improvement?
HashiCorp Terraform state management could be improved to be used efficiently with multi-users. Even though there are logs, there are always issues I've seen with people manipulating the TerraForm state. We cannot work efficiently with the solution if the state is incorrect. Due to certain reasons, if I have to change some piece of some resource, I cannot change it. I have to destroy the whole thing and then build a new one.
For how long have I used the solution?
I have been using HashiCorp Terraform for three years.
What do I think about the stability of the solution?
HashiCorp Terraform is a stable solution. I rate HashiCorp Terraform an eight or nine out of ten for stability.
What do I think about the scalability of the solution?
Around 20 users are using HashiCorp Terraform in our organization.
I rate HashiCorp Terraform an eight or nine out of ten for scalability.
How was the initial setup?
HashiCorp Terraform's initial setup is simple. Especially with TerraForm Cloud, you don't have to do anything since it's a SaaS platform. Also, TerraForm Enterprise is easy to install.
What about the implementation team?
HashiCorp Terraform's deployment is very easy and doesn't take much time.
What was our ROI?
We have seen a return on investment with HashiCorp Terraform.
What's my experience with pricing, setup cost, and licensing?
HashiCorp Terraform's pricing depends on the way people use it. Not everyone uses the solution the way HashiCorp recommends to use it. HashiCorp Terraform goes by workspaces, and workspaces are more expensive than nodes. The nodes are cheaper.
People implement the solution in different ways. So you can use the solution with less money and make it cheaper, but that's not the recommended way. If you use the solution according to the recommended way by HashiCorp, it is more expensive.
What other advice do I have?
I am using the latest version of HashiCorp Terraform.
I recommend users build the framework and the modules correctly right from the beginning. Then, build the workspace as recommended by HashiCorp. According to HashiCorp's recommendation, one workspace should exist per application or environment. That's how people need to build it.
Then, modularize everything and make custom modules for the organizations. Especially things that stay out of the application, like security, network, and compute, should be in separate modules. Later, they can be brought into the application.
Overall, I rate HashiCorp Terraform an eight out of ten.
showing 11 - 20