Different Mold Makers, Same Underlying Principle

Opening Scene

Several different manufacturers might produce brick molds, each with its own specific design and manufacturing process, but all built around the same underlying principle: consistent, repeatable production. Choosing between manufacturers is a genuinely practical decision, even though the fundamental value proposition is shared across all of them. Choosing between infrastructure as code tools involves this exact same kind of practical, vendor-specific decision built on shared underlying principles.

In Plain English

The major infrastructure as code tools share the declarative, idempotent principles covered earlier in this series, but differ in practical, meaningful ways: Terraform is cloud-provider-agnostic, using its own configuration language across virtually any provider; AWS CloudFormation is native specifically to AWS, tightly integrated with that provider’s services; and Pulumi allows infrastructure to be defined using general-purpose programming languages like Python or TypeScript, rather than a dedicated configuration language.

The Old Way

Before this range of mature IaC tools existed, options for implementing these principles were considerably more limited:

Early infrastructure automation tools were often more limited in scope, tightly coupled to a single provider, or lacking the mature ecosystem these tools have since developed.
There wasn’t yet a well-established range of tools letting organizations choose based on genuine tradeoffs like multi-cloud support or preferred programming language.
Organizations sometimes had fewer practical options for implementing declarative, idempotent infrastructure management consistently.

Limited, less mature tooling options, without today’s range of practical choices, is what the current landscape of mature IaC tools directly addresses.

What’s Changing (and Why AI Is the Reason)

Organizations increasingly choose deliberately among Terraform, CloudFormation, Pulumi, and similar tools based on genuine tradeoffs: multi-cloud portability, provider-specific integration depth, or preferred programming language.
This connects directly to the multi-cloud IaC practice covered in Article 17, where tool choice, particularly provider-agnostic tools like Terraform, directly affects genuine cross-provider portability.
As AI-assisted code generation tools increasingly need to produce infrastructure definitions, tools like Pulumi, using general-purpose programming languages, sometimes offer a more natural fit for AI code generation than dedicated configuration languages.

The Metaphor, Fully Extended

The Brick Mold	Infrastructure as Code Concept
Different manufacturers, each with a specific design	Different tools, each with a specific approach and ecosystem
Built around the same underlying principle of consistent production	Built around the same underlying declarative, idempotent principles
A genuinely practical decision between manufacturers	A genuinely practical decision between Terraform, CloudFormation, and Pulumi
Shared value proposition, meaningfully different specifics	Shared core principles, meaningfully different practical tradeoffs

For Beginners: What to Actually Do

Practice researching the basic differences between Terraform, CloudFormation, and Pulumi in terms of provider support and configuration approach.
Learn to recognize that all major IaC tools share the same declarative, idempotent foundation covered earlier in this series.
Get comfortable with the idea that tool choice is a genuine, practical decision worth researching, not an arbitrary preference.

For Practitioners and Leaders: The Deeper Layer

Evaluate IaC tool choice explicitly against your organization’s genuine needs: multi-cloud portability, provider-specific depth, or team language preference.
Connect tool choice directly to the multi-cloud portability goals covered in Article 17 if cross-provider flexibility is a priority.
Consider whether tools using general-purpose programming languages offer a better fit for teams increasingly relying on AI-assisted code generation.

Quick Recap

Terraform, CloudFormation, and Pulumi share declarative, idempotent principles but differ in practical, meaningful ways.
Terraform is provider-agnostic; CloudFormation is native to AWS; Pulumi uses general-purpose programming languages.
Tool choice should be driven by genuine organizational needs, not arbitrary preference.
AI-assisted code generation may favor tools using general-purpose programming languages in some cases.

Where This Fits in the Series

Article 6 covered the practical landscape of major IaC tools. Article 7 turns to a concept every one of these tools depends on: the master record of what’s actually been built.