3 ms·
That's not true. Immutable infrastructure state should not be dependent on previous state because there is no state. It's remove and replace only. If there's a
by kodah 3y ago
That's not true. Immutable infrastructure state should not be dependent on previous state because there is no state. It's remove and replace only.
If there's a piece of infrastructure that cannot be regarded as immutable and this is mimicking immutability behind an API (like a CDN) then it's not immutable. Understanding this and segregating that infrastructure away from totally immutable components (like servers, functions, load balancers, etc) is key.
The CDN mutability probably can be flushed out by some processes like etags but the most important problems are solved, just hard.
- klysm 3y agoWhat tools are you using to accomplish this? Can’t be terraform
- kodah 3y agoAs I said, you need to know how that infrastructure is built. Terraform is just fine. If you call to spin up a VM with a disk that's been imaged to a standard, that is immutable. Functions can also be made immutable by programming in a way that takes into account potential shared state.
- klysm 3y agoTerraform works by tracking mutable state though which was my point
- kodah 3y agoAh, state is relative in this context. A VM lacks state when you determine the starting state. A function lacks state depending on how you code it and the contracts you have. A CDN is always stateful. Sometimes the Terraform state overlaps with an entities internal state but most of the time not. "Immutable infrastructure" state refers to internal state, not Terraform state.
- klysm 3y agoAh I see what you mean and I agree it’s possible to achieve immutable infrastructure in that sense.