Immutable vs Mutable Infrastructure: Replace vs Patch

Mon, 03 Aug 2026 05:18:27 +0900

Overview

Immutable infrastructure treats servers as disposable artifacts — every change ships as a brand-new image that replaces the running instance rather than editing it. Mutable infrastructure instead updates in place, applying patches and config changes directly to long-lived servers. The choice determines how predictable, auditable, and drift-resistant your environments are.

Comparison Diagram

Comparison Table

Aspect	Immutable Infrastructure	Mutable Infrastructure
Initial provisioning	Instance built once from a versioned image or template	Instance provisioned once, then edited repeatedly over its life
Applying a change	Rebuild the image with the change baked in	SSH in, or run a config-management tool, against the live server
Deployment mechanism	Orchestrator replaces old instances with new ones (rolling/blue-green)	Update scripts or agents (Ansible, Chef, Puppet) mutate the running instance
Configuration drift	Cannot occur — every instance matches its source image exactly	Accumulates over time as ad hoc changes diverge from documented state
Rollback	Redeploy the prior image version, deterministic and fast	Manually reverse changes on the server, often incomplete or unreliable
Emergency hotfixes	Requires rebuilding and redeploying an image, slower to react	Can be patched directly on the box in seconds
Auditability & reproducibility	Image is a versioned artifact; environment is fully reproducible	True state only knowable by inspecting the live server
Pipeline & storage overhead	Needs an image build pipeline and artifact/image registry	Lower tooling overhead, no build pipeline required

Key Differences

Immutable instances are never touched after launch; mutable servers are patched in place.
Immutable infrastructure eliminates configuration drift by construction.
Rolling back immutable infra just means redeploying a prior image version.
Mutable infra depends on ongoing config management tooling to keep state converged.
Immutable workflows require an image build pipeline and registry that mutable setups skip.

When to Use Each

Immutable Infrastructure

Configuration-Management on IT Comparison

Immutable vs Mutable Infrastructure: Replace vs Patch

Overview

Comparison Diagram

Comparison Table

Key Differences

When to Use Each