If you follow cloud2030 discussions or any of my podcasting over the last decade, Edge is a very interesting topic to me. Today’s episode is a short update on the state of the edge from a very specific position.
In this discussion, I walk through with Josh why edge has been hard for us to nail down from a technology perspective. This is something of special interest to RackN as we keep honing and refining our IT edge infrastructure technology set.
How do Edge and Compute and SaaS and cloud influence everything that we do? We covered topics from VMware explorer and talked a lot about Edge. That led to AI ml, which led to another topic, which led to another topic.
If you enjoy hearing about how interconnected our technology and choices are, everything from Bitcoin to edge, and cloud and government interaction, this is the podcast for you because we cover pretty much all of it and connect it together.
Remember that on September 14, we are having one of our quarterly book club meetings on the death of expertise.
In the Cloud 2030 podcast episode from August 24th, CEO Rob Hirschfeld discusses the shift from the rental/service economy to owning production assets in the context of cloud and SaaS models. He highlights the financial commitment and decoupling of capital expenses associated with service usage, emphasizing the value of owning assets in certain scenarios. Hirschfeld encourages deliberate decision-making regarding asset ownership, stressing the importance of understanding the long-term consequences and skill-building for businesses. He invites listeners to explore these topics further in the complete August 24th Cloud 2030 conversation.
We break down the edge compute cluster by the Chick-fil-A team, and we talk about how they use Kubernetes, specifically K3s in 2500 of their restaurants to build an IoT and restaurant management system. This system uses Intel Knucks, a commodity commercial residential grade hardware.
It’s an update on a four year old Kubernetes story with a lot of buzz, and they show how they have been successful building this system.
If you’re interested in Kubernetes, Edge DevOps and distributed systems, this episode has a lot to enjoy.
In the Cloud 2030 podcast episode on Chick-fil-A’s Kubernetes control plane, Rob Hirschfeld highlights the challenges and benefits of transitioning cloud infrastructure and applications to edge locations using commodity gear. He emphasizes the success of Chick-fil-A’s approach in bringing cloud tools and platforms to non-cloud environments, showcasing the potential for mapping cloud processes back into edge computing. Hirschfeld encourages listeners to explore the detailed discussion on Chick-fil-A’s edge clusters and engage in broader conversations on Cloud 2030 at the2030.cloud.
We get an update for the first time in four years about Chick-fil-A edge Kubernetes clusters that gets to the heart of how building distributed infrastructure works and what the challenges are.
We had a fantastic conversation about laying the foundations for this. We came away with two really important thoughts about what edge infrastructure looks like, how you pick it, can Kubernetes be used, what is IoT and integration, and the design considerations that go into building this environment.
Listen to this podcast as a preview for a longer article.
We do a 2022 retrospective slash 2023 prediction episode – a sort of end of the year classic for us, except our predictions and look ahead are different from most people’s.
We’re looking at some broader trends around software, build materials, impact of GPT (which will be a future episode), edge Technology, cloud adoption, security, faults and failures.
Not your garden variety look back look ahead type of show.
How is data center infrastructure adapted to edge distributed ledger technology workloads?
We think through if those demands (blockchain, proof-of-stake coins, etc) are changing the way we look at data center infrastructure, and the short answer is yes. We also explore the impacts of the type of workloads that we’re running and how we distribute them, rather than the type of equipment that we need to buy.
This conversation quickly becomes one about what we want to do with our infrastructure, not what the infrastructure is.
Today’s episode is about measuring complexity. Complexity is a topic that we cover a lot. And in this case, we really went past the idea that we could measure complexity, and into looking at the causes and costs of complexity.
We had a remarkable conversation about what it means to say something’s too complex? What are the consequences of complexity? And what should we do about them? Ultimately, it’s about how how we measure the cost or the risk of complexity?
In the end, we are reframing complexity in business terms and human terms. That is the important approach to looking at complexity.
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.
We started talking about blockchain and the edge, but that is not where it ended up at all! Our fascinating journey started with web3, and surprisingly, it’s potential for distributed infrastructure and distributed web.
That led us to edge: managing and trusting devices on the edge through distributed ledger (DLT). That led us to the distributed ledger landscape. The journey is important because some of these technologies will be essential for establishing trust in systems.
In this conversation, we walk through the progression of these very important topics.
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.
