As core contributors and maintainers of the popular CNCF project, wasmCloud, we’re excited to work towards the next major milestone in the evolution of this awesome community platform. In the next couple of posts, we’ll take a look back at how far we’ve come, and look ahead to what we can expect from wasmCloud 1.0; our standards-led, production-ready release due to be unveiled in early 2024.
wasmCloud now comes with experimental support for Go, via TinyGo compiler, taking full advantage of the WebAssembly component model. This is an exciting moment as, for the first time, Go developers can build cloud native Wasm applications with components and run them in wasmCloud in an open, dependency-free and standards-based way.
This year, wasmCloud is getting into the spooky spirit by participating in Hacktoberfest! Our primary development repositories all feature the hacktoberfest topic. Whether you’re interested in your first open source contribution, learning Rust for the first time, getting involved with a WebAssembly project or seasoned in all of the above, you’re invited to participate!
We're a big fan of bumping minor versions here at wasmCloud. When we released our first version of the Elixir/OTP host, we bumped from 0.18.0 to 0.50.0 just to make it extra clear that this was a big change. Today, we're making a similar bump to 0.78.0, and this blog post will explain why.
wasmCloud uses GitHub actions to publish all of its example WebAssembly modules and first-party capability providers to AzureCR. Neither of these are actual containers, nevertheless they conform to the OCI image specification and can be distributed well with the existing OCI tooling in the cloud native ecosystem.
The first thing people need to learn when encountering WebAssembly for the first time is how to interact with the code inside the module. There are a number of patterns available for this and, in this blog post, I'll cover the main three: Command, Reactor, and Library.
When we model data structures and encode business logic into our applications, we generally use either a functional programming model or an object-oriented one. In a single process, this choice can be a matter of personal preference, but in distributed systems this choice can actually have significant impact.
The world of WebAssembly (Wasm) runtimes has evolved quickly over the last couple of years. In this short update, we'll cover the factors that drove us to transition to Wasmtime as the most natural choice to underpin wasmCloud.
We should always plan to take advantage of the benefits and clarity offered by hindsight, reflection, and learning from what came before. In this post, we take a look back at where we started, where we've been, and take a peek at where we're going.
The actor model is a model for concurrent computation originally developed in 1973. This classic definition says that in response to a message, an actor may: