#immutable infrastructure

[allengeer]

[allengeer]

Axel Fontaine, Flyway creator and Boxfuse's CEO, discusses Immutable Infrastructure and whether it's ready for the prime time. Fontaine discusses architectural and organizational concerns and explains why containers may not always be the best solution for all infrastructure problems.

[theagileadmin]

Immutable Delivery

This article proposes a design pattern modeled after “Immutable Infrastructure”, something I call “Immutable Delivery”.  There has been a lot of debate and discussion about the usage of the term “Immutable” lately. Let me clearly say that there is no such thing as an immutable server or immutable infrastructure. I know of no example in my 35 years of working with IT infrastructure of a system or…

View On WordPress

[ritwiksblog]

After Docker: Unikernels and Immutable Infrastructure

Haven't really seen unikernels explained this simply (although to be fair, I've been too busy learning other things to pay attention whenever I did see it mentioned). With the AWS stacks at work, I've spent some time this year moving us towards an immutable infrastructure architecture - deploying and building images programmatically, defining their configuration code, etc. It's not perfect, I had no idea what I was doing at the beginning and just learnt as I built (so there's lots of room for improvement), but I definitely already see the benefits of it.

Unikernels are an interesting next step to that, fully clearing out any cruft your image doesn't need, down to the OS / kernel level. It makes sense intuitively, but it's still in the early stages of adoption, so I guess it will depend on whether we get easy tools for working with them. With basic immutable infrastructure ideas, docker / vagrant / puppet / etc make it really easy to try out and start moving parts of your system to that model.