Mutable Infrastructure

In this lesson, we’ll explore how HashiCorp Packer integrates into application deployment by comparing mutable and immutable infrastructure paradigms. Understanding mutable infrastructure is the first step toward seeing the advantages Packer brings.

What Is Mutable Infrastructure?

Mutable infrastructure refers to servers (physical or virtual) that are continuously updated and modified after initial provisioning. A typical workflow looks like this:

1. Develop your application code.
2. Provision a server instance.
3. Install the operating system (e.g., CentOS, Fedora, Ubuntu).
4. Install packages and dependencies.
5. Harden and secure the server (firewall rules, user permissions).
6. Deploy and start your application.
7. Maintain with ongoing patches, upgrades, and configuration tweaks.

Each in-place change mutates the system state, and over time, these mutations can lead to inconsistencies across servers.

while (alive) {
  eat();
  sleep();
  code();
  repeat();
}

Challenges of Mutating Live Servers

Applying updates or security hotfixes directly on running servers may work at small scale but leads to:

• Human error: Manual updates on many servers increase the risk of typos and missed steps.
• Configuration drift: Minor differences accumulate, causing environments to diverge and making debugging harder.

Automation tools like Ansible mitigate some risks by orchestrating parallel updates. However, since servers still mutate in place, drift can persist.

Comparing Mutable vs Immutable Infrastructure

References

• HashiCorp Packer
• Ansible Documentation
• Immutable Infrastructure Patterns