Tag Archives: Cloud

Serverless vs Digital Twins

We discussed the intersection of serverless and digital twinning. These two concepts are really tightly intermingled!

We discarded the idea of a central single serverless hub managing everything; instead, we think sites would actually have a mesh of serverless, interconnected event processing and stream processing systems. This approach is much more function dependent, but really opens up a lot of interesting discussions and possibilities.

We also discussed how to manage all of this meshed, serverless subscription modeling eventing, and digital twinning.

Transcript: otter.ai/u/FWW3CwG6gMX0N06QXp9C-pZd-s8
Image: www.pexels.com/photo/two-young-g…-sweater-9532902/

Cloud2030ServerlessCloudDigital TwinsModelsAI/MLEvent ProcessingDistributed SystemsEdge

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 roundtable discussions, shares insights from the January 13th discussion on serverless and digital twinning. He emphasizes the significant overlap between modeling data through digital twinning and building serverless systems that subscribe to events for action, transformation, and control. Hirschfeld underscores the need for a joint discussion on these topics, highlighting that a sustainable serverless system requires a reliable model, and a useful digital twin system must connect inputs and outputs to the real world. Interested listeners are invited to explore the full episode at the2030.cloud for a comprehensive discussion on these critical industry aspects.

Can DevOps Be More Collaborative / MSFT & Activision

We have a lot of questions about improving collaboration in organizations:
How do we deal with change in organizations
How can we get organizations to work together better?
How do we encourage collaboration around the automation spaces that we’re trying to build in DevOps.

In our discussion, a lot came back to something as simple as version control!

We also discuss how we handle coupling between systems. In order to collaborate, we have to couple systems. But if we couple them, we create complexity.

This podcast includes our warm up conversation about Microsoft acquiring Activision because that is ALSO about how you integrate to organizations and business plans! This was news of the day and I think you’ll be very interested in our take on it.

Transcript: otter.ai/u/itNrmoL9MgG980D8CZdo9XWd-xI
Image: www.pexels.com/photo/a-woman-pla…ith-kids-7176471/

Exploring Edge Applications

This episode explores applications for the edge. We really try to dig in on what will work in the edge from an application perspective. We also explore what’s holding us back.

Every time we have a conversation about Edge, we help undangle the components of Edge. In this discussion, we get more concise about what type of infrastructure is needed to build real edge applications. We also define where edge applications are expected to work and where they don’t.

Transcript: otter.ai/u/7uwv5Z3aupwE5ZGBXBEUqw9zkbE
Photo: www.pexels.com/photo/red-and-bla…ot-statue-185725/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, offers insights from the December 2nd Edge Applications discussion. The conversation focuses on the challenges of building integrated edge applications composed of various components like platforms, compute, networking, and sensors. Hirschfeld highlights the need for collaborative data planes, digital twins, and an ecosystem that allows applications to utilize existing resources, emphasizing that these challenges in the edge space have yet to be fully addressed. He encourages listeners to explore the comprehensive discussion at the2030.cloud.

Is Edge HCI Necessary?

To explore HCI at the edge, we started with SUSE’s Harvester. It’s an HCI integration of Kubernetes, KubeVirt, and Longhorn (their storage system) plus some PXE booting magic they threw in there. From there we explored how Kubernetes can fit into Edge HCI.

That really morphed into Edge operations more generally. It’s not clear if hyperconverged infrastructure can or can’t fit. We covered items like AWS Outpost which is Amazon’s edge. We included items for the cloud to edge migration from an application development perspective.

There are a lot of fascinating ops and development topics throughout the conversation.

Transcript: otter.ai/u/Y2OH7SuJhPp4VRQSBAJk31-0_eI
Photo: www.pexels.com/photo/crop-person…ontainer-4498143/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, provides insights from the January 4th discussion on hyper-converged infrastructure (HCI) for the edge. The conversation explores the operational desire for clean and simple architectures with modular building blocks for easy implementation. However, it challenges the notion that platforms like Kubernetes can create a straightforward, self-building architectural solution for edge clusters, emphasizing the associated cost considerations. Hirschfeld suggests exploring the full episode at the2030.cloud for a comprehensive discussion on the complexities and potential solutions in the realm of hyper-converged infrastructure for the edge.

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.

A Pathway to Standardization

This episode was a fun and interesting ride from boring standards to locking APIs via NFTs!

We started talking about “civilization technology” where standards and regulations are applied to infrastructure. We are expecting this to happen in cloud (eventually) because it allows us to create ecosystems around the infrastructure. The historical patterns that we see in railroads, buildings and electricity will emerge in IT too.

Or maybe they won’t! We haven’t yet seen standards emerging in cloud or open source. And we had some really significant conversations around the interactions between these systems that would drive or resist standardization.

Transcript: otter.ai/u/-hhn6VEjtIQDl3UAHaCPUxCUaXo
Photo: www.pexels.com/photo/slatted-woo…en-trees-1423827/

Evolution of Networking Systems

How do we evolve technology in the future?  We centered the answer on networking, but in a very general way.

The ability for a vendor to distribute technology and then connect things together and then build networks of that technology is a core component of how networking is evolving.   Ultimately, this is about building technology systems.

Sadly, that led us into a very dark place where we really thought through who’s going to own all of that infrastructure and their motivations.  How can we make sure that the people’s needs and the systems and the vendors’ needs are well aligned?

Transcript: https://otter.ai/u/H8ik1HcmSExVBRklYbSCsV4yu2k

Image: https://www.pexels.com/photo/shallow-focus-photography-of-keychains-1194036/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, reflects on the November 2nd DevOps Lunch and Learn session, which explored the motivations and impacts of building highly networked systems. While acknowledging the significant societal benefits of interconnected technology, Hirschfeld emphasizes the importance of understanding and mitigating the potential risks, particularly regarding data control and accessibility. He advocates for building inclusive systems that prioritize adaptability and service to the greater good, inviting listeners to explore the comprehensive discussion on these critical topics 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.

What is Platform Engineering?

What is platform engineering? And why is it necessary and how to make it work compared to DevOps.

In this conversation, we really hit on the challenges of creating automation teams for building automation in scalable ways. Frustratingly, we never really came up with a particularly good answer to “what is a platform team” and why you should care. Strangely, your organization is probably building one.

Transcript otter.ai/u/zJeQbqXIyD8kZUxfKQdvQAfQGog
Image: www.pexels.com/photo/building-co…chnology-9617733/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, reflects on the November 9th DevOps Lunch and Learn session focused on platform engineering. He highlights the challenge of executing platform engineering initiatives despite the straightforward concept of improving automation and tooling at an architectural level. Hirschfeld emphasizes the importance of defining success metrics, empowering teams to enforce standards, and adopting consistent, repeatable patterns and practices to advance the industry’s maturity. He encourages listeners to explore the insightful discussion at the2030.cloud for a deeper understanding of platform engineering’s significance.

A Path for Cloud Standardization?

We discuss standards, de facto standards, and cloud standards. It comes down to how we are creating repeatable results for the cloud marketplace.

Ideally, we’re creating marketplaces where standards can be shared. We’d consider Amazon as the primary example, but we also talk about hardware and Kubernetes which have their own marketplaces.

Ultimately, we asked if we are creating standardized cloud infrastructure? The short answer is no.

Transcript: otter.ai/u/kGT8pGfbslZRgFktM0pE3AifwWI
Image: www.pexels.com/photo/measuring-g…tar-pick-3988555/

Rob’s Hot Take:

Rob Hirschfeld, CEO and co-founder of RackN and host of the Cloud 2030 Podcast, reflects on the November 30th DevOps Lunch and Learn session focused on standards and vendors’ attempts to establish standard operating processes. He highlights the market’s lack of convergence or trust in vendor-driven standards, emphasizing the durability of certain influential standards in the industry compared to vendor-specific APIs. Hirschfeld underscores the ongoing need for standard operating models and APIs to address market complexity, encouraging listeners to explore the insightful discussion at the2030.cloud for deeper insights into standardization efforts within the industry.