We use the solution mainly for infrastructure as code (IaC) and to securely store a backend file. We can also use it to provide role-based access to users, whereby they can only access certain resources with a certain access limit. The solution is more secure than other storage platforms like GitLab or Bitbucket.
The solution's most valuable feature is infrastructure as code (IaC). When you want to create any resource over the cloud, it usually takes a lot of time and sometimes results in manual errors. There'll be an error whenever we perform something manually over a console.
When I use Terraform instead of using a console to create the same infrastructure, it will simplify my work. I can use the same script repeatedly to create multiple resources of the same kind, which makes my work simpler.
HashiCorp Cloud Platform is an enterprise solution. It would be good if college or university students could explore HashiCorp Cloud Platform to a certain extent as an open-source solution. This would enable them to work on it directly when they come to the industry rather than needing a knowledge transfer.
I've been using the solution for a couple of years. I work in a service-based industry where my clients completely rely on HashiCorp Cloud Platform.
I haven't encountered any issues with the solution's stability. However, when I host it on a server with multiple users, I may encounter some latency issues.
I rate the solution’s stability eight and a half out of ten.
The solution provides seamless scalability. The solution works seamlessly when multiple users use the same script to practice scripting and versioning.
The solution is worth the money.
The solution's pricing is moderate according to industry standard prices.
The solution's integration capabilities are seamless. I can use it to efficiently store the state file in Google bucket and AWS bucket.
Anyone can use the solution. However, you need some experience to follow best practices and use it efficiently and securely. You also need experience to keep the modules in a separate file and securely store the values and variables in a separate file.
Initially, when I started learning the solution, I faced some challenges. Suppose a client previously used the solution, and the cloud had some feature limitations. If the client wants to enhance their resources, I need to update the modules to the recent version and make changes accordingly to the variable files or modules, which is pretty time-consuming.
I would mainly recommend the solution for startups with fewer employees. It allows them to reuse the code and provides good utility. They can directly get into the workflow instead of spending lots of time on the landing zone setup or initial intra-creation.
Overall, I rate the solution eight and a half out of ten.
