Enzo Nocera is a Wasm enthusiast. He has experience working for many cloud providers but his work with wasmCloud is more of a personal passion.
Enzo has an exciting project which integrates Wasm (Wasmtime right now but later wasmCloud) with the Leptos project. The Rust ecosystem has been evolving in the background and so Enzo is demoing a full-stack framework to create backend and frontend applications with a single Rust codebase.
The aim was to prove we can use the same codebase to build a server side and browser side service based on modern Wasm standards.
2 WASI contracts - filesyetem to serve static asets and WASI HTTP to stand up the server.
Super reative web app that runs entirely with Wasm as a demonstration of how quickly we can deploy web pages, and how we can build in backend integration.
This is one of the nicest experiences we've seen in building a front-end app with back-end integration. Well worth checking out in the repo.
Still WIP but Enzo will share the details in Slack.
As always, it's really hard to express the joy of the demo - check out the recording below for Enzo's session, and ensuing community questions.
This is V2 of the components crate which incudes HTTP wrapper.
This was spurred by improved support for Wasm P1/P2 on a stable toolchain in Rust - this means it is a much nicer experience when starting and compiling with or without wash build.
Brooks shows what the experience looks and feels like now the Rust toolchain is a little more mature.
This has now been published to our documentation as a template.
Now, rather than using wit-bindgen, we can use the wasmcloud-component crate when we're writing in Rust.
Completely interoperable with existing HTTP crate functionality.
Check out our new and improved Quickstart where you can find more details and get hands on. You can get a feel for what it feels like to write this kind of code.
It's super tricky to represent the demo in notes - check out the recording below for Enzo's session, and ensuing community questions.
DEMO and DISCUSSION: wkg: how it works + what's next?
wkg (pronounced "wackage") is a package manager for WIT interface files created as part of the wasm-pkg-tools initiative from the Bytecode Alliance. It is comparable to NPM or Cargo, but for building and running applications with components.
wkg manages WIT dependencies packaged as OCI artifacts which means any organization that already has an OCI registry can access, store and call standard WIT interfaces.
Now available in wash 0.36.0!
wkg is now used directly in wash - very exciting as this means it automatically manages your dependencies - declared in a WIT world.
You just run wash build and it will automagically fetch the dependencies required - locked insde a wasmcloud.lock file.
This is a great example of how the Wasm component model lends itself to automation by exposing component dependencies from the start.
If you want to convert from wit-deps or commit the deps directory in this model and need some assistance, head on over to Slack.
Time flies when you're a wasmCloud maintainer. We have made some significant progress in the roadmap and you can follow progress here.
Notable issues: we have xloisethe omponet sdk go is already in the wild and we've closed several other issies.
wasmCloud.toml can exist in alternative directories which adds an additional layer of flexibility and repo cleanliness.
Open PR: host running mutiple lattices. New contributor: working on tab autocomplete for resources in wasmCloud. Human time values - new contribution - super cool.
New Quickstarts for Rust and Typescript
We are on track to deliver what we wanted to this quarter. If there is anything fokls wannt to take but you need more info, please come and join us on Slack. Or visit wasmCloud Contribute which shows all the good first issues to get stuck in.
UPDATE: Wasmcon + KubeCon + CloudNativeCon, what's on and where to find us
WasmCon and KubeCon + CloudNativeCon NA are around the corner and we have put a blog post together which details all the talks from our users, maintainers and industry colleagues. It also details where and when we'll be manning the wasmCloud project booth (Wed 13th, afternoon and evening through KubeCrawl).
We are super excited to see so many talks from wasmCloud users, maintainers and community collaboratoes. As before, WasmCon and KubeCon + CloudNativeCon NA are around the corner and we have put a blog post together which details all the talks and where we will be!
If you’re going to Salt Lake City for WasmCon and KubeCon + CloudNativeCon NA why not tune in to the Rancher Labs podcast where our Taylor (and Salt Lake City local) will share his tips on visiting #SLC, and what to expect from this year’s conference.