Category Archives: Supply Chain

CHIPs Act And Global Supply

How do we build advanced innovative products and companies? We discuss the Chips act and global supply chain of silicon and manufacturing in today’s episode.

We took that apart into its component parts: supply chains, raw materials, power, whether talent, real estate, and put it back together in ways that look forward towards how we think these forces and global politics are going to shape manufacturing for the next decade.

Absolutely fascinating and critical discussion that will impact every single person’s health, their careers, and frankly, what they can buy on the store shelves.

Transcript: otter.ai/u/JPNiGOfYD8WZzyqGcbQ9y4biN5k
Image: www.pexels.com/photo/closed-up-p…ing-unit-1432680/

Rob’s Hot Take:

In the August 18th Cloud 2030 discussion, Rob Hirschfeld delves into the complex factors influencing technology innovation, including geopolitical considerations, weather, supply chain dynamics, and the significance of the CHIPS Act. The conversation explores the potential impacts on innovation, particularly in the semiconductor industry, and debates whether the CHIPS Act will lead to increased vertical integration by large companies or foster innovations in smaller-scale manufacturing methods like 3D printing. Hirschfeld highlights the disruptive nature of the CHIPS Act and its potential to reshape supply chain dynamics, encouraging listeners to explore the full episode at the2030.cloud.

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/

Rob’s Hot Take:

In the April 12th episode of the Cloud 2030 Podcast, Rob Hirschfeld delves into the nuanced discussion of whether Kubernetes prevents or exacerbates vendor lock-in. The key takeaway is that lock-in is not inherently negative, and there’s a need to balance risks and consider the inertia associated with established systems and practices. The podcast encourages listeners to think intentionally about using Kubernetes as an abstraction layer and to recognize the value and challenges of inertia in platform development efforts. For further insights and discussions on DevOps and future strategies, visit the2030.cloud and join the conversation.

Migrating Long Term Applications

How should we think about migrating legacy workloads to new infrastructure and modernize them?

The group addresses this question methodically incuding how databases get linked, how they get used, how they get migrated, how important it is to maintain languages and what it would take to migrate in language. In the end, we look back on that conversation apply lessons learned to what we are building today,

This is absolutely essential because new designs will become tomorrow’s legacy! We’ll be struggling to migrate those in 10 or 15 years too. So everything we can learn helps prevent that cycle.

Transcript: otter.ai/u/sHB8507KjZlZPBMToBUCEKjPVQY
Photo: www.pexels.com/photo/man-and-wom…tainside-8968077/

Rob’s Hot Take:

Hello, I’m Rob Hirschfeld, CEO and co-founder of RackN, providing a hot take on the January 25th discussion about migrating legacy applications to the cloud. While the topic may seem limited, the reality is that today’s legacy was once a cutting-edge application, underscoring the importance of designing with future migrations in mind. The key challenges identified in the conversation were complexity and coupling, emphasizing the need for clean, referenceable APIs to facilitate smoother migrations. To delve into these insights further, listen to the full episode on January 25th and join the ongoing discussions at the2030.cloud.

Reliable License Models

We talk about software licensing in open source, and what it means to the broader market. In fact, we cover how it’s changing what the market actually is!

This is not not just open source licensing in general because at the end we didn’t care about the license. We are more concerned about utility, serviceability and operability of the products we use. We need to understand whether or not we can rely on them!

In short, the supply chain of the software was much more important than the licenses of the software

Transcript: otter.ai/u/kH-vbVxoymH9GGdNEi3jvF07c5s
Image: www.pexels.com/photo/gray-planes…om-window-127441/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, reflects on the October 28th discussion about software licensing. He highlights the industry’s indifference towards software licensing as a critical battleground and questions the necessity of open source for good software, asserting that system support, maintenance, and trusted partners are more crucial. While acknowledging the importance of community goods like Kubernetes for creating abstraction layers, Hirschfeld emphasizes that the ultimate focus should be on the supply chain and invites listeners to explore the extended conversation at the2030.cloud.

Resolving Software Dependency Chains

Dependency chains are complex and fragile when you’re depending on software, hardware cloud services that go away or change. In this conversation, we really examine the challenge of having dynamic vendor relationships and what we can do to fix and protect our environments.

It’s really hard to fix what can be vulnerable when it also changes your software supply chain at any moment! And that can impact any device in your infrastructure!! We work through that problem means in practical terms.

Transcript: otter.ai/u/mwpwVINGYfkQ5F5IERXgsM2oHsA
Photo: www.pexels.com/photo/focused-kid…d-puzzle-5063480/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, reflects on the January 11th DevOps lunch and learn focused on managing dependencies in technology. The discussion reveals a critical realization that the interconnected and short lifecycle of technology components results in a near certainty of repercussions when patching or updating one part of the infrastructure. Hirschfeld highlights the serious security and continuity risks associated with unmaintained projects, emphasizing the need for improved visibility and management of software dependency graphs. He encourages listeners to explore the comprehensive conversation at the2030.cloud for insights into addressing these challenges.

Software Supply Chains [#Log4Shell]

Our scheduled topic was supply chains generally, but the Log4Shell vulnerability dominated the discussion. We dove into the challenge of patching and fixing a library that is literally in nearly every device or service for years and years.

That led us to supply chains in the context of software, and specifically Java Log4j. This is a critical topic and our conversation about it was very thoughtful. We really covered the angles of what it takes to produce and maintain a supply chain for software. Then we discussed alternatives and things to consider when you building anything: software products or physical products in which embedded systems and components impact your designs.

Transcript: otter.ai/u/CJ8pYF1La6tetFasqZhEojo_zoY
Image: www.pexels.com/photo/carton-cont…-in-rows-6294430/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, reflects on the December 16th discussion centered around the supply chain, particularly focusing on Log4j and software components. He underscores the importance of understanding the provenance of software components and emphasizes the necessity of maintaining a robust patch and update process, especially considering embedded systems like Java. Hirschfeld advocates for a shift in mindset towards viewing software as an ongoing process rather than a static deliverable, inviting listeners to explore the insightful discussion further at the2030.cloud.

Broader Impacts of AWS Outage

We discussed the Amazon outage of December 7. Instead of simply blaming Amazon, we went looking for how the outage impacted people globally. We considered how hyper scalars are being treated and how these outages can be avoided or understood. We focused on who is impacted and what companies who are building on top of Cloud providers can do going forward.

We really took a classic Cloud 2030 approach for a very important and timely topic. Enjoy our discussion about the business impacts, understanding of the market and forward looking approach.

Transcript: otter.ai/u/cY4fk8mWIovIfkwfT4LDw2uy4QY
Image: www.pexels.com/photo/a-person-ho…ked-eggs-7719168/

Rob’s Hot Take:


Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, provides insights on the December 9th discussion regarding the Amazon outage on December 7th. Fresh from the outage’s impact, Hirschfeld highlights the industry’s reliance on cloud providers as utilities and underscores the need to acknowledge their business interests, which may not always align with customer needs during disruptions. He advocates for building resilience both at the provider and consumer levels, emphasizing the importance of understanding and mitigating the risks associated with hyperscale infrastructures. Hirschfeld invites listeners to explore the comprehensive conversation at the2030.cloud, focusing on industry-wide reflections rather than attributing blame to specific providers.

Securing Software Supply Chains

Today we talked about supply chains, but mainly security and the security aspects of supply chains because we have a very serious challenges here.

We have made software and on boarding software for developers so easy, but haven’t put the same efforts in how to manage production systems! The team really talked about what it takes to build production systems that respect security, supply chains, dependency graphs, and inclusion in a way that cross teams.

It’s an incredibly important topic, and it is the foundation of any successful supply chain hardening effort.

Transcript: otter.ai/u/6zfld2gBpZMSGT8Vk_1Ka3pWtN0
Image: www.pexels.com/photo/light-city-…traffic-10390684/