AWS CloudFormation vs. FlexMMS vs. IBM Terraform

I still give it an 8 because it's one of those tools that just quietly does the heavy lifting for you but it can really test your patience when it breaks esp with deep nested stacks. It's perfect for projects where we need clean consistent environments every time. It's less ideal for quick experimental setups like new EC2 configs or Lambda permission tweaks.

Incentivized

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.

Incentivized

• All resources can segregated based on stacks which provides greater visibility
• A complete audit trail of what went wrong while deploying a particular resource
• Automatically rollbacks if any service as part of CloudFormation results in an error
• The UI tool is useful

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

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

• The language itself is a bit unusual and this makes it hard for new users to get onboarded into the codebase. While it's improving with later releases, basic concepts like "map an array of options into a set of configurations" or "apply this logic if a variable is specified" are possible but unnecessarily cumbersome.
• The 'Terraform Plan' operation could be substantially more sophisticated. There are many situations where a Terraform file could never work but successfully passes the 'plan' phase only to fail during the 'apply' phase.
• Environment migrations could be smoother. Renaming/refactoring files is a challenge because of the need to use 'Terraform mv' commands, etc.

Incentivized

It's easy enough to get a shared template & apply it. You don't even have to download-then-upload or copy-and-paste, a publicly-accessible url works.

Diving deeper, it has enough powerful capabilities to make the life of a platform / DevOps engineer bearable.

However, you need equally deep knowledge to troubleshoot issues, when they inevitably pop up. This is the same for all IaC technologies, as they are additional abstraction layers on top of the native API provided by the cloud providers.

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

I have yet to have an opportunity to reach out directly to HashiCorp for support on Terraform. However, I have spent a great deal of time considering their documentation as I use the tool. This opinion is based solely on that. I find the Terraform documentation to have great breadth but lacking in depth in many areas. I appreciate that all of the tool's resources have an entry in the docs but often the examples are lacking. Often, the examples provided are very basic and prompt additional exploration. Also, the links in the documentation often link back to the same page where one might expect to be linked to a different source with additional information.

Incentivized

Cloning a virtual machine creates a virtual machine that is cloning a virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Cloning a virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information. Management guide.For information copy of the original. The new virtual Cloning virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource Management Guide. For information is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource Management Guide. For information

Incentivized

Terraform is the solid leader in the space. It allows you to do more then just provisioning within a pre-existing servers. It is more extensible and has more providers available than it competitors. It is also open source and more adopted by the community then some of the other solutions that are available in the market place.

Incentivized

• + We can standup a VPC in minutes
• - It took a lot of inital time to set up
• + With logging/rollback, made testing much easier.

Incentivized

• we are able to deploy our infrastructure in a couple of ours in an automated and repeatable way, before this could take weeks if the work was done manually and was a lot of error prone.
• having the state file, you can see a diff of what things have changed manually out side of Terraform which is a huge plus
• if state file gets corrupted, it is very hard to debug or restore it without an impact or spending hours ..
• writing big scale code can be very challenging and hard to be efficient so it's usable by the whole team