 Next up we have Liam Randall. He is the CEO and of Cosmonic and he is a Wasmcon co-chair. He's also a serial entrepreneur and these days he's working on a web assembly. He's going to talk to us a little bit about the component model. Please welcome Randall. I mean Liam Randall. All right. Is everybody excited? I know that I am. So my name is Liam Randall. I'm the CEO of Cosmonic and I love all things web assembly. I'm a father of three co-chair of this event, Wasm Day and I'm so excited to look out across this room and see not competitors but so many collaborators because I hope that the theme of today's entire conference really embraces the better together. The theme that Ralph Scalacci and I launched a few years ago when we did the original web assembly keynote. So let's get started. And before we do, this talk is going to be a little different. I had donated some of my time to Luke. So I'd ask everybody to take your phone out of your pocket. We're going to make this talk interactive and we're all going to play with web assembly components live. Demo gods be praised. All right. And we're going to use CNCF Wasmcloud and open source project that we're announcing today has full support for the web assembly component model. I want to start with a quote. Learn from the container wars is that we were fighting each other too early in the process. There was this mindset that the winner would take all. The truth is the winner takes all the burden. And that is a short quote from one of the luminaries, one of the fellow veterans of the container wars. You know, I was there. I served with your father, you know, back in the day in Kubernetes land. I actually had an early Kubernetes startup that I sold in 2016. Little bit notes to me that people would still be getting into Kubernetes today. So I asked us all to take a deep breath and pause and recognize that this story really is the better together story. And with the web assembly component model, we finally have our docker moment. We have a common format, the component, that enables us to collaborate and work together. Finally, we're not competing on language SDKs. We're all aligned on raising the abstraction for everybody in the ecosystem. And today's demo, we're going to be using CNCF wasm cloud, which originally came out of Capital One. It was open source in 2019. We just launched a new Rust host and it's on its way to 1.0 and incubating in the CNCF. It's compatible with Kubernetes, but not dependent upon it. I'm going to use a couple different tools today for demonstrations, but all of them underneath the hood work with CNCF wasm cloud. That's what we're going to be orchestrating today. So take your phones and everybody get this QR code. Let's deploy some components. If you watch the little demo on the left, you'll see a couple quick steps, just off with your favorite off provider here, and then click deploy now. And what's going to happen is you're going to deploy web assembly components for the first time. And hopefully it works. It's a very simple application. What it will do is just let you grab a random XKDC comic and deploy it. Now, let me pause for a moment, and there will be much more content about this later, but let's talk about what these web assembly components really are. The web assembly standard actually has two specifications. Modules, which are the executable component, and Wats, the human readable piece. Components are simply just modules with the interface definition at the end. And what that enables us to do is to have this common view of the world that I think we've all really centered around. This idea that while wasm itself, as Bailey Hayes says, is just three integers in a trench coat, web assembly components, now let us start thinking about LEGO blocks. And when we start thinking about LEGO blocks, we suddenly realize how many of today's constraints were suddenly freed from in this model with web assembly components. The one that wasm cloud really focuses around is freeing your application architecture from a tight coupling to the application topology. Think about your development life cycle. That simple app, did anybody successfully deploy that? All right, got a couple people down here that were able to click through and get their application deployed. Think about the development life cycle of that simple app pictured here at the top. You might start developing that on your Mac and think of these components as LEGO blocks. But you might want those LEGO blocks to be separated or scaled across multiple VPCs on the left, or even running it across Kubernetes on the right. An orchestration standard that's included in wasm cloud enables us to do that very easily. So let's do another example. Let's do a really tiny one. I've taken three web assembly components and deployed them actually around the United States. We're in Seattle, in AWS East in Virginia. I'm running a web server. And in Azure, down in Texas, I'm running a little another web assembly component here. And on stage, right here on my badge, I'm running a third web assembly component. This little device right here. So everybody take your phones. Then we've got to be praised. And this may be crazy, but here's my QR code, curl me maybe. And when you curl me, whatever you send in that request will actually pop up here on my badge. So let's see if anybody gets it. Okay, I see some messages coming across. So people are actually connecting. Think about the path of the packets that you just took. You're in Seattle on this conference Wi-Fi. You went all the way out to Virginia into AWS onto Wasm Cloud, which uses NATS, down to Azure from Azure in Texas, back over this Wi-Fi to the badge running on my chest, where we responded in just a couple milliseconds. If that doesn't let you know that the web assembly component model is ready for prime time, I don't know what is. So a tiny example. And if you don't really trust my QR code, you can also hit me at Liam.Wasm.WTF, which is my quick way of announcing that Cosmonica also supports custom domains. So you can continue to hit that throughout the conference if you want to send me a message. I'll put it next to my bedside so you can wish me good night or anything else. But what about the really hard problems? What about bigger infrastructure? What about telco? What about energy systems? Financial services? Transportation? Does this model really hold true for these areas as well? And the answer is that regulated organizations actually suffer the most. They're the ones that are absolutely crucified on the crippling common complexity that's inherent in containers. The idea that we embed libraries at compile time instead of runtime, the tight coupling to specific CPUs, services, and application typologies, the cold start time measured in seconds versus microseconds. And put together a quick demo here that also runs across an imagine telco environment and three live clouds. I don't really have time to go through it in huge detail, but if you come by our booth, you can come see the rest of this where we're going to orchestrate web assembly components and machine learning both on the edges and in the cloud as well. So I hope you'll join me in exploring the web assembly component model this week as we sort of understand the impacts of capability-driven orchestration, policy-based component execution, and how web assembly orchestration can help us template and scale infrastructure to new heights. But most of all, as we pursue our common cause here, that all of us, every startup and company in this room just wants to raise the abstraction, that components are the ladder for us to get there, and that we'll work together to make web assembly better together. Thank you so much for your time.