cloud2030

How do we make data centers green because, fundamentally, they are going to use electricity. But the sources of that electricity, how we respond to shortages of electricity and cost signals about that electricity are all critical to consider. These are the questions that lead us to how a green data center or green infrastructure gets created. Our discussion also includes how infrastructure at the edge can play a role. Overall, there are A LOT of the factors that go into building and creating green infrastructure, including the motivations and signals that will hopefully change the market. Transcript: https://otter.ai/u/9eirv3Rs292n7M1m8d1VaRPPRgA Image: https://www.pexels.com/photo/clear-light-bulb-planter-on-gray-rock-1108572/

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/

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: https://otter.ai/u/CJ8pYF1La6tetFasqZhEojo_zoY Image: https://www.pexels.com/photo/carton-container-with-eggs-in-rows-6294430/

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: https://otter.ai/u/cY4fk8mWIovIfkwfT4LDw2uy4QY Image: https://www.pexels.com/photo/a-person-holding-a-pan-with-cooked-eggs-7719168/

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 https://otter.ai/u/zJeQbqXIyD8kZUxfKQdvQAfQGog Image: https://www.pexels.com/photo/building-construction-industry-technology-9617733/

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: https://otter.ai/u/kGT8pGfbslZRgFktM0pE3AifwWI Image: https://www.pexels.com/photo/measuring-guitar-pick-3988555/

Serverless at the edge, part one. This is a dynamic and engaged conversation with key questions like: What is serverless? Do we need serverless? How is edge serverless different than cloud serverless? We see edge environments as collecting data from sensors that needs to be heterogeneous, multi vendor, dynamic and centralized. But where centralized? I think that the serverless aspect of this really drives home the idea that we need to be able to make small, quick, easy updates into an edge environment into a sensor environment. But how we accomplish that is still to be defined. Transcript: https://otter.ai/u/XOOi-HhvbqC6NG16-7ns6j_hPLE Image: https://www.pexels.com/photo/man-in-white-long-sleeve-shirt-holding-a-serving-tray-3772524/

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: https://otter.ai/u/6zfld2gBpZMSGT8Vk_1Ka3pWtN0 Image: https://www.pexels.com/photo/light-city-road-traffic-10390684/

We explored Operations Value mapping. This lead to an a very interesting discussions of complexity budgets and how to measure complexity budgets. This includes managing supply chain, and value pipelines, and system coupling. Complexity budgets could be a very powerful measuring tool for understanding operations value In an organization. Overall, this helps you explain the cost of complexity to organizational leadership. Transcript: https://otter.ai/u/T1jXorfZO6Yc7fovBEXKgxSnxao Image: https://www.pexels.com/photo/old-map-of-iceland-on-wall-4338273/

Today's episode is about supply chains but with a Cloud2030 twist. We focused on forward leaning futures by looking into how supply chains are being disrupted. It's going to be hard to get them working again if they can ever come back! Transcript: https://otter.ai/u/fBMFUh1TtBwdFvh7q0tKgpwW7kA Image: https://www.pexels.com/photo/buildings-cars-city-cross-harbour-tunnel-262100/