7
DevOps
Terraform vs Pulumi for infrastructure as code
Ecosystem ↔ Expressiveness
Context
Our infra is click-ops in the AWS console plus a few CloudFormation stacks. We're standardising on IaC. The application team writes TypeScript and likes Pulumi. Platform folks know HCL.
TerraformvsPulumi
Community verdict
Terraform 67%Pulumi 33%
9 engineers · 2 opinions
With these constraints, what would you choose?
One choice per engineer. You can change it any time.
Terraform
Pulumi
Expressiveness →
Trade-offs
Dimensions
TerraformPulumiout of 5
- Ecosystem
- 5Terraform scores 5 of 53Pulumi scores 3 of 5
- Expressiveness
- 2Terraform scores 2 of 55Pulumi scores 5 of 5
- Hiring
- 5Terraform scores 5 of 5
Community discussion
2 comments
Have you made this decision in production? Share your reasoning.
Sign in to commentPulumi let our app engineers own their own infra in the language they use daily, with real unit tests. Platform stopped being a bottleneck.
Terraform (or OpenTofu) is the lingua franca. Every module, every Stack Overflow answer and every new hire knows it. HCL's limits are a feature: infra code stays boring.