The Benefits of Immutable Infrastructure

Mar 31, 2017 by Armory

Immutable Infrastructure: The practice of replacing your infrastructure with new instances each time you deploy new code to ensure mutated code does not carry forward.

  • How does this benefit my company?

Immutable infrastructure makes server maintenance as easy as installing fresh new copies of your servers into the cloud and deleting your old versions when it’s confirmed that the newer ones are up and running.

Below is a short list of benefits immutable infrastructure may provide you:

  • Your company is preparing to run cloud-native applications
  • You are trying to automate the scaling of your infrastructure in the cloud
  • You want simple and infinitely repeatable deployments
  • Continuous deployments safely and quickly (Netflix deploys 4000 times a day!)
  • The operations becomes more automated and responsibility falls on the developers
  • Server and node failures do not result in your service going down for long, if at all
  • When would my team use it?

Every time your team wants to deploy new code and upgrade your servers it should be good practice to install fresh copies of your infrastructure instead of simply injecting your code onto existing ones.

Think of your infrastructure like a house: over time things break and become dented as you bring in furniture and remodel things. You can paint over scratches and fix leaky faucets (updating existing infrastructure) but the age will eventually show in ways you don’t expect – such as creaking floorboards or carpet imprints – and users notice these things. Practicing immutable infrastructure is like building a brand new identical house each time you introduce an item, but without the cost and effort of building an actual house!

  • Do my services have to commit all-in?

No: just like how some companies are only hybrid-cloud, it is possible to use hybridized immutable infrastructure.

This post is part of a series of posts that describe features in Spinnaker. You can find
all of the related posts here.

Learn More

Recently Published Posts

How Armory Uses Makelog to Drive New Feature Adoption from Day One

Jun 23, 2022

original post For teams that practice CI/CD and ship multiple times a day, waiting weeks to communicate these updates to customers defeats the purpose. After all, if a feature ships and nobody knows about it, did it really ship? You miss out on delivering value to customers sooner, learning which features they’re most excited about, […]

Read more

Armory Continuous Deployment-as-a-Service is Now Available

Jun 6, 2022

Over the last two years, our customers and prospects have said one thing: everyone wants Continuous Deployment, but adopting CD to production is too hard for many companies. Today we’re excited to announce that Armory is making production-grade continuous deployment available to all users of Kubernetes, regardless of size. Armory Continuous Deployment-as-a-Service has been in […]

Read more

Introducing OpenCost—An Open Source Project for Monitoring Kubernetes Spend

Jun 2, 2022

We are excited to share the launch of OpenCost, an open source project that provides real-time cost monitoring for teams running Kubernetes workloads.   As container and Kubernetes adoption continues to grow, navigating the complexities around measuring and allocating cost is becoming a business-critical challenge. A recent CNCF survey showed overspend is increasingly a problem for […]

Read more