Declarative vs imperative IaC in Terraform - Visual Side-by-Side Comparison

Process Flow - Declarative vs imperative IaC

Start

↓

Choose IaC Style

↓

Declarative

↓

Describe Desired State

↓

Tool Figures Out Changes

↓

Apply Changes Automatically

↓

Infrastructure Matches State

↓

Imperative

↓

Write Step-by-Step Commands

↓

Run Commands in Order

↓

Infrastructure Changes as Told

↓

Result Depends on Commands

This flow shows the choice between declarative and imperative IaC. Declarative means you say what you want, and the tool figures out how to do it. Imperative means you tell the tool exactly how to do each step.

Execution Sample

Terraform

resource "aws_instance" "web" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
}

# Imperative: aws ec2 run-instances --image-id ami-123456 --instance-type t2.micro

This shows a declarative Terraform resource block describing an AWS instance, and an imperative AWS CLI command to create the same instance.

Process Table

Step	Action	Declarative Behavior	Imperative Behavior	Result
1	Define desired state or command	Write resource block with desired instance	Write CLI command to launch instance	Both specify instance details
2	Run tool	Terraform plans changes to match desired state	CLI runs command immediately	Terraform plans; CLI acts now
3	Apply changes	Terraform creates instance if missing	Instance created by CLI command	Instance launched in both
4	Update or change	Change resource block, Terraform updates instance	Run new CLI commands step-by-step	Declarative auto-updates; imperative manual
5	Delete	Remove resource block, Terraform destroys instance	Run CLI terminate command	Instance removed in both
6	Exit	Infrastructure matches declared state	Infrastructure matches commands run	End state depends on approach

💡 Execution stops when infrastructure matches desired state (declarative) or after commands finish (imperative).

Status Tracker

Variable	Start	After Step 3	After Step 4	Final
Infrastructure State	No instance	Instance created	Instance updated or unchanged	Matches desired or commanded state
Terraform Plan	Empty	Plan shows create instance	Plan shows update or no change	Plan empty after apply
CLI Commands Run	None	Run launch instance	Run update or terminate commands	Commands complete

Key Moments - 3 Insights

Why does Terraform plan changes before applying?

Terraform compares current state to desired state and plans only needed changes (see execution_table step 2). This avoids unnecessary actions.

In imperative IaC, what happens if a command is missed?

The infrastructure may not reach the intended state because commands must be run in order (see execution_table step 4). Manual steps can cause errors.

Can declarative IaC handle updates automatically?

Yes, by changing the resource block and reapplying, Terraform updates resources as needed (see execution_table step 4). Imperative requires manual commands.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Terraform create the instance?

A Step 5

B Step 1

C Step 3

D Step 6

💡 Hint

Check the 'Declarative Behavior' column in execution_table at Step 3.

According to variable_tracker, what is the infrastructure state after Step 3?

A Instance created

B Instance updated

C No instance

D Instance terminated

💡 Hint

Look at 'Infrastructure State' row after Step 3 in variable_tracker.

If you skip running CLI commands in imperative IaC, what happens?

A Terraform fixes the state automatically

B Infrastructure may not match desired state

C Commands run themselves later

D Infrastructure is deleted

💡 Hint

Refer to key_moments about missing commands in imperative IaC.

Concept Snapshot

Declarative IaC: You describe what you want; the tool figures out how to do it.
Imperative IaC: You write exact commands to do each step.
Terraform is declarative; AWS CLI is imperative.
Declarative tools plan changes before applying.
Imperative requires manual command execution.
Declarative reduces errors by managing state automatically.

Full Transcript

This lesson compares declarative and imperative Infrastructure as Code (IaC). Declarative IaC means you write the desired end state, and the tool figures out the steps to get there. Imperative IaC means you write exact commands to run step-by-step. Terraform is an example of declarative IaC where you write resource blocks describing your infrastructure. The tool plans and applies changes automatically. Imperative IaC, like using AWS CLI commands, requires you to run each command manually in order. The execution table shows how Terraform plans and applies changes, while imperative commands act immediately. Variable tracking shows how infrastructure state changes after each step. Key moments clarify why Terraform plans first, the risk of missing commands in imperative IaC, and how declarative IaC handles updates automatically. The quiz tests understanding of when instances are created, infrastructure state changes, and consequences of skipping commands. The snapshot summarizes the key differences and behaviors of declarative vs imperative IaC.