Mutable And Immutable Objects And Resources Explained

What are mutable and immutable objects and resources? Does immutability apply to bare metal, virtual machines (VMs), applications, Cloud, containers, infrastructure, Kubernetes, etc.? What does mutability and immutability mean? Mutable vs. immutable explained.

#Mutable #Immutable #Containers #Cloud

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

▬▬▬▬▬▬ 💰 Sponsoships 💰 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Courses, books, and podcasts 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Introduction To Mutable And Immutable
04:23 Pros And Cons Of Mutable Infrastructure
09:08 Pros And Cons Of Immutable Infrastructure
14:48 Where To Apply Immutable Approach?

[DevOpsToolkit]

How do you manage your applications, services, and infrastructure? Are you fully mutable, fully immutable, or something in between?

IMPORTANT: For reasons I do not comprehend (and Google support could not figure out), YouTube tends to delete comments that contain links. Please do not use them in your comments.

[edenr]

Great explanation Viktor 👌 funny enough I was discussing it just today with my team. I couldn't find a better explanation, I'll share it with my team.
I also think that modern programming languages like Rust have this concept built-into the language natively, by default Rust make all variables immutable unless specified otherwise and that's for a reason. I like your explanation..
Thanks for sharing! 👍

[jNtMbi]

valuable content @Viktor thanks for sharing

[wollginator]

Great topic! I personally think immutability based on GitOps plus application (Kubernetes) and infrastructure (Cluster API / Crossplane) reconciliation is the way to go! Btw, Talos OS is 1.0 GA now!

[mknights]

One of the creative freedoms I experienced when moving from Java to Scala was immutability. For me software is about confidence in the programming: for a user confidence that my input will be processed consistently, for a developer that the language will give me consistency in its application of my intent as described by syntax. It’s the same for infrastructure and deployment… as a user I want reliability and certainty that things will be consistent. It doesn’t have to be slow to recreate infrastructure with a small change if we consider higher order functions in DevOps - a function that creates a function.
Crossplane for example uses the interpreter pattern to take declarative syntax and execute functions in a specific context to build infrastructure. The future of solutions such as crossplane may well be to lift those functions into higher order functions and place them in monadic structures that enable greater composition of types and effective flat mapping into a resultant function. This would enable greater opportunity for evaluation (think terraform plans) of the resultant crossplane AST calling providers.

[mknights]

In you question about the future. For me we are heading to a point where we must not consider these Lego block containers but instead we are compiling application code, configuration and resources (IO components) into an execution context. That execution context can the released into any provider much like byte code with apps.