Immutability means replacing deployed infrastructure instead of changing it in place. Like an immutable object, a server is replaced with a new version when it needs an update; logging in to patch a live server is the mutable approach to avoid. section 9.8.1 section 9.8.3
Replacing servers brings practical benefits:
- Consistent environments: build staging and production from the same blueprint to prevent configuration drift. section 9.8.3
- Simpler rollbacks: reroute traffic to the previous frozen server instead of hurriedly undoing changes. section 9.8.3
- A breached server’s installed backdoor disappears when that server is destroyed and rebuilt. section 9.8.3
Patch the version, not the server
If a security patch is needed, don’t log in to the live server and install it. Build a new server with the patch, then replace the old one. This avoids leaving behind undocumented changes. section 9.8.1
There is an important boundary: application servers should be stateless and immutable, but live databases hold persistent customer data. They cannot simply be destroyed and rebuilt for an operating-system patch; their changes require care. section 9.8.3



