Defending Against Complexity With Exercise

How do you manage complexity? Something we talk about a lot in Cloud2030 is how challenging it is to understand complexity, measure it and cope with it.

Richard Cooke wrote a paper called “How Complex Systems Fail,” (how.complexsystems.fail) and in it he talks about complex systems having strong defense mechanisms against failure. That’s what we talked about today. How do we build defense mechanisms for complex systems, not by making them simpler, but by exercising them and testing them?

We discuss the importance of testing, validation, and layer of abstraction and testing the layers in this conversation. If you deal with complex systems, this discussion will be fascinating and actionable.

Transcript: otter.ai/u/SP-z7OAJWAmJlql8Dh62rNk2hlo
Image: www.pexels.com/photo/man-woman-m…ng-young-4058411/

Why Jenkins in DevOps?

What kind of orchestration systems does the industry use for infrastructure, automation and controlling day to day operations?

In today’s episode, we talk about infrastructure pipelines at the tooling level, and specifically the use of Jenkins and other CI pipelining tools for ops and orchestration. We dig into why and how you would do this, and what pieces are missing from the system. That conversation leads us into larger day to day challenges.

If you are doing infrastructure ops and DevOps automation, you will get a lot out of this session.

Transcript: otter.ai/u/dbTdHdYTIt5bU1G8SFghKSijhU0
Image: www.pexels.com/photo/barista-wit…d-tattoo-6205639/

Green Data Centers

What’s going on with green data centers, why does it matter, and how do we think about it in a wider context? In this short conversation, we discuss green data centers and creating carbon neutral infrastructure.

This isn’t just about servers using electrons – the actual conversation about making our infrastructure carbon neutral includes thinking about all of the components that go into our infrastructure.

We also have an upcoming series of conversations on green data centers and carbon neutral infrastructure.

Transcript: otter.ai/u/IYsPlr4r570MmOOW3WWLjenDlWk
Image: www.pexels.com/photo/clear-light…ray-rock-1108572/

OSS, Promotions, and Lava Lamps

How can promotion boards be hostile or hurtful to open source technology? We talk about the dynamics of corporate support in open source technology, and if being rewarded for internal work at companies translates into challenges for open source technology.

This discussion starts to peel apart what makes open source technology sustainable, and what it works for. We bring up an analogy of a lava lamp where things heat up and then cool down as part of a natural cycle, which can be a normal cycle for all software, and that led us back to how promotion boards work.

We covered a lot of ground through the dynamics of corporate software governance and open source and interweaving those together.

Transcript: otter.ai/u/nZS6rtcam88JUuqMctOiEyWq5G4
Image: www.pexels.com/photo/food-cold-d…nk-glass-5677999/

APIs With Composable State

What makes API’s complex? In this episode, we talk about how we compose APIs into higher level systems, and how we think about the design elements that go into building durable, reusable API’s.

This is a classic topic for us, and in this discussion we looked beyond the API itself and started talking about the state of the system and how you manage that state.

Transcript: otter.ai/u/Oae5e_ay0d_l48TmWk3PO3lpIDU
Image: www.pexels.com/photo/a-nacho-chi…ng-sauce-5848731/

Can Kubernetes Prevent Vendor Lock In?

How does Kubernetes create lock in versus how could Kubernetes be used to prevent lock in?

Lock in is not always a bad thing. When you avoid committing to a single vendor, you may have to work to the lowest common denominator or deal with heterogeneity in your infrastructure. Heterogeneity is pretty normal, and you might have to do this work regardless, but when you commit to a vendor you get to focus on using the vendor’s strengths.

In this episode, you’ll pick up some great tips on how to reduce your lock in when using Kubernetes.

Transcript: otter.ai/u/vIo1p15bb6VmcrWjwgOLbM25nq4
Image: www.pexels.com/photo/silhouette-…door-knob-792032/

Orchestration Automation Workflow [with Terraform]

Building reliable automation at scale for infrastructure presents challenges. In this episode, we discuss orchestration, workflow automation, and the reconciler pattern in the context of Terraform.

We refer to the pattern of Terraform, automation, and orchestration systems as “TACOS” and today we dig into how you test it and check it against drift. These are real topics of operational concern for anybody building any type of infrastructure.

Transcript: otter.ai/u/w-NA0HBsTc5NRaqWQQwlWUj4Whw
Image: www.pexels.com/photo/person-hold…ith-food-8448079/

Everything As Code !

What makes Everything as Code and Infrastructure as Code interesting? In today’s episode, we discuss what makes something code-like and the idea of Everything as Code, based on Patrick Dubois’ article “In depth research and trends analyzed from 50+ different concepts as code.”

Reference: www.jedi.be/blog/2022/02/23/tre…0-as-code-concepts/

Some of our conclusions were practical, like if a concept is a process that is reproducible and auditable, that’s what makes it code-like. And some other possible conclusions were that it’s just marketing because it makes everything programmable. The reality is somewhere in the middle.

Transcript: otter.ai/u/E1TezO2XutwJyS-vCNetslwWO4A
Image: www.pexels.com/photo/man-in-grey…icky-note-879109/

How Lock in Creates Risk

Organizations take a risk when they get locked into a vendor. In today’s episode, we talk a lot about the risks of lock in, both in general and in the context of Oracle.

That discussion takes us into a question of insurance, and if insurance policies could ultimately drive people to reduce lock in exposure. This was a fascinating discussion, not only about lock in but about what would drive organizations to fix their lock in problems.

Transcript: otter.ai/u/zJf0WMUwJgamk7IpscHCsL2vsV4
Image: www.pexels.com/photo/closed-white-door-3119977/

Goldilocks Platforms [w James Urquhart]

A Goldilocks’ balance challenges us to trade off prescriptive and flexible platforms. James Urquhart shares his experiences with Cloud Foundry, VMware, and Amazon about trying to find the right balance between building it yourself versus a prescriptive service approach.

We’ve decided that there needs to be a middle zone with enough opportunity for customization, as well as enough pre-set, prescriptive methods to create sustainability.

In this episode, we talk about that balance and how different processes have done it in industry.

Transcript: otter.ai/u/OQBfCHldtYjUpqjKdkN3KjzLiR0
Image: www.pexels.com/photo/brown-teddy…h-outside-207891/