Some thoughts and reflection on my first day using Wasm components for something more involved than hello world.
Engineering @ Cosmonic
This post will outline the reasons why Nomad is an ideal container orchestrator for WebAssembly and wasmCloud, and how we created Netreap to run Cilium in our Nomad clusters alongside the rest of our infrastructure. In my next post, I'll walk you through how to run Cilium on a Nomad node, and how Netreap performs in practice.
An examination of how wasifills—a component adapter pattern like polyfills, but for
components—can help bridge the gap between today's rapidly changing standards landscape and the
future of interoperable components facilitated with
wit and wit
worlds. It's an amazing time to
be on the bleeding edge of the WebAssembly adoption curve, but it's not without risk.
At the Pasadena leg of Kubernetes Community Days (co-located with SCaLE 20x), I had the chance to talk to 100 or so Kubernetes enthusiasts, to give my perspective on WebAssembly, through the lens of a Kubernetes veteran.
There are several new standardization efforts happening within the WebAssembly (Wasm) space, including what we believe to be a new way to write software applications. By way of describing this new model, I would like to dive into some of the history of Wasm as a way to describe where we are heading.
An engineer begins her Monday, sitting down at her desk with a cup of coffee. She's feeling productive, inspired, and ready to write some good code. She opens her GitHub inbox to find 42 notifications on her projects, like this one:
⚠️ CRITICAL VULNERABILITY: Upgrade
garbodep from 1.1.12 to 1.1.13
garbodep? I don't even directly depend on that, why am I getting notified for this?" And
so, her day begins.
My list of projects and technologies to get into the lab for learning and experimentation is never-ending. However, this holiday gave me just enough time to take another look at Microsoft Orleans, a technological kindred spirit with wasmCloud.
With the recent release of the .NET Framework 7, I thought it might be a good excuse to check back in on the .NET WebAssembly ecosystem and see where things stand and what improvements have been made.
From the beginning of our days developing wasmCloud, we took a stance to be compatible with today's technology without being dependent on it. So, wasmCloud needed to be able to:
- Run inside or outside of a container
- Run inside of Kubernetes or another orchestrator and run without it
- Run on Linux, but also support Mac and Windows (and not just WSL)
Here at Cosmonic, we believe that WebAssembly is the future. In talking to developers we found that many people still have questions about why WebAssembly would be useful for them. We partnered with our friends at Suborbital and Fermyon to write a blog post answering why we think WebAssembly is so compelling. Check out the blog post on Wasm Builders!
Keep up to date
Subscribe to Cosmonic for occasional communication straight to your inbox.