 Hey everyone, welcome to the CNCF wasm cloud project update. We are a sandbox project in the CNCF primarily under the application platform or the scheduling and orchestration section. I like to say that we're in the same category as Kubernetes just a smaller box kind of all the way in the bottom right corner. So that's very fun. You all have probably heard of the word cloud before but not all of you have heard of wasm before so I always love asking this question who has heard of WebAssembly or wasm in this room? Actually I love the ratio of that going out every single year so I will do a quick just run through on what wasm is just for the folks who haven't heard of it because it's important it is the core piece of the wasm cloud project which is our unit of compute for the application platform and it really is just like a tiny virtual machine you write code in a language of your choice you compile it to WebAssembly instead of a native binary or something that you would execute as a script and then it can run on anywhere that a wasm runtime can run which is a browser or on the server side on x86 on arm etc. So this is really important for us in order to work as an app platform our actual applications are composed of WebAssembly components and what that is is basically just a small little piece a small architecture and operating system agnostic binary it actually does look like assembly but like I said you're just writing code and then compiling it to that and every single WebAssembly component has a set of imports and exports you can kind of think of this like the CFFI boundary that's how it actually gets things done and we operate with a set of common imports and exports like HTTP blob store key value logging these common application components that you use in cloud native applications every day so these components you can not only build applications with them you can compose them together which is a core piece of how we have you know if you have multiple different microservices in your application they talk to each other over this component boundary and the really important part of this is in the WebAssembly specification in the standard is a very strong security boundary that's driven by these common interfaces and these different components actually don't share anything when they run so that is a little bit of a preamble in preview it sounds like a lot of people knew about WebAssembly already which is awesome so just to get into what the wasm cloud project is it is both a platform and we have associated tools like an orchestrator for declarative deployments it's completely cloud edge and platform agnostic so this is just a binary that you can run on linux mac or windows we distribute a container we can run in kubernetes it's really important for us as an app platform to not be tightly tied to a specific cloud specific platform you can extend it with your own capabilities in addition to the common ones like HTTP servers and blob stores the things that you need for your application to run and what we actually do is under the hood we use another CNCF project called NATS for all of our networking and RPC back and forth between components at runtime and so what this creates is this really nice flat platform that you can orchestrate applications across they can communicate together at runtime the same if they're running on one computer as they are across different availability zones different regions very simple to test we're also very into reinventing the entire wheel when it comes to application the binary so running as WebAssembly is very different than running with a regular binary but we love to integrate with existing standards existing CNCF projects wherever possible so we distribute our artifacts using OCI you can just store regular old wasm components in OCI registries we use open application model for our declarative manifests we are completely hotel observable so logging metrics traces comes out of the box for your applications from day one and we use cloud events as a standard format for all the things that happen in our system all those things are really nice to combine together into a cloud native project so we are in addition to integrating with common cloud native standards we are a leading integrator of a standards compliant WebAssembly platform so the standards that come out of the WebAssembly specification and the cloud the server side standards and the WebAssembly system interface we implement all of those we're huge on what comes out of the CNCF and the bytecode alliance and it's really important for us to keep that going to be an open and standards based platform we're seeing a lot of growing industry adoption as WebAssembly and our project matures we've been going and doing WebAssembly things on the server side since about 2019 so we've been doing this for for quite a while which is when I started on with the project and we've been security audited and had passed that which was great I'm seeing adoption in a variety of Fortune 100 companies some of them which you could see talking at wasm day today so I like I like to say we've got integration with standards we've got the good old yamalon slides something like this will look fairly familiar it's it's a manifest for how we would define a WebAssembly small application so we're running a component from an OCI registry and we are linking that component to an azure blob store component at runtime of course no demo for today but this is kind of what it looks like to lay out a small WebAssembly application not too different than like a case deployment and this is all kind of done declaratively we also good old yamalon slides we also have a kubernetes operator which we've been working with which is really nice you can interact with these WebAssembly resources natively with your qctrl commands you can define the way that you want to run the topology of those actual wasm cloud hosts which is really nice just to have that kubernetes native integration and last but not least the last thing I want to talk about today is that we have been in sandbox for a little over what day is it little over three years now so we have applied for incubating which we think that we're really excited to move to that next step within the cncf so I think that's all that I have for you today so maybe next year I'll see you at the the incubating project talks thanks folks