It’s Friday, and I’m writer’s blocking trying to write up something persuasive defending the concept of Immutable Infrastructure in DevOps. Really, the client in question has at best Semi-Immutable Infrastructure: updates can be applied via the deployer for the systems that are now working under that paradigm. They don’t tear down the and rebuild their VMs for patches and security updates. And they still have a lot of stuff that works under the traditional “mutable” model.
But we are pushing the idea of eventually having all IT infrastructure adopt DevOps principles. For major OS or software releases, or in the event of a security breach or other problems with the system, tearing the system down and rebuilding it should be done. I approach DevOps from a traditional IT background. Most of my colleagues approach it from developer backgrounds. I’ve found that traditional IT folks are more resistant to DevOps principles than people with developer backgrounds. So I feel like when IT people exhibit skepticism, having “come to Jesus” myself from the same heresy, I should be the one to preach to them the DevOps gospel.
I’m curious if anyone out there has worked in this area. My current focus is doing a large, legacy database system as Immutable Infrastructure. Or at least Semi-Immutable Infrastructure if you’re a real purist (which I am not).