9 articles tagged with Infrastructure As Code.
One is agentless and Python-based, the other two run a persistent agent and a domain-specific language. The architecture difference matters more than the syntax.
Terraform, OpenTofu, Pulumi, CDK, CloudFormation, Crossplane, and Ansible each solve a different slice of the IaC problem. This is how they compare on license, language, state, and cost.
Terragrunt keeps large Terraform setups DRY and orchestrated, but small teams often pay its learning curve for little return.
Both Pulumi and AWS CDK let you define infrastructure in real programming languages, but they split hard on multi-cloud, state, and engine maturity.
A practical look at Spacelift, env0, Atlantis, and Scalr for teams outgrowing HCP Terraform on price, policy, or OpenTofu support.
Terraform provisions infrastructure and Ansible configures machines, so pitting them against each other is the wrong question to ask.
A practitioner's comparison of Terraform and CloudFormation on AWS covering state, drift, new-service lag, rollback, and where CDK fits.
Terraform's declarative HCL and Pulumi's real programming languages solve the same problem in very different ways, and the right pick depends on your team.
HashiCorp relicensed Terraform and a community fork spun up overnight. Here's how OpenTofu actually differs and which one your team should run.
