Community Calls
WebAssembly Composition & the Wasm Component Model in wasmCloud
The March 19, 2025 wasmCloud community call centers on the Wasm component model — both at build time and over the lattice. Brooks Townsend demos how to compose WebAssembly components with the wac plug tool, then shows new wash build functionality (in a PR) that performs the same composition automatically using WAC's Rust library, so developers never have to install or learn the CLI. The call then turns to a community proposal from LUK3ARK: "virtual components," a way for components to route invocations over wRPC to services that live outside the lattice — and the security questions that raises.
wadm Config Reconciliation, the Single wash CLI & KubeCon EU
The March 12, 2025 wasmCloud community call is a tooling-focused update for anyone building on the Wasm component model. Brooks Townsend demos a wadm reconciliation fix that takes local application deploys from around 15 seconds down to under one second by reacting to configuration events instead of waiting for a heartbeat. The team also marks the completion of the long-running merge of wash-cli and wash-lib into a single wash crate, previews wasmCloud's presence at KubeCon EU and WasmIO in Barcelona, and digs into tracing and observability for capability providers.
WebAssembly News: Merging the wash CLI and SBOM Build Provenance
The March 5, 2025 wasmCloud community call is a short, heads-down WebAssembly news update from a team in KubeCon EU crunch mode. Brooks Townsend walks through the in-progress effort — led by maintainer Ahmed — to merge the wash CLI and wash-lib crates into a single wash crate so features ship faster, and explains why the team is holding a feature freeze until the PR lands. Masoud, a wasmCloud OSS Fellow, shares phase-one progress on SBOM and build-provenance work for wasmCloud artifacts, which sparks a discussion with Taylor Thomas about keeping component builds compliant with the OCI artifact standard.
Custom Interfaces, Distributed RPC Errors & the Wasm Component Model
The February 26, 2025 wasmCloud community call digs into the Wasm component model and the realities of distributed computing. Brooks Townsend demos a proposal for handling transport-level failures in custom interfaces — a well-known RPC error type, defined in WIT, that lets a WebAssembly component gracefully catch errors like a missing link, an unreachable target, or a disconnected NATS, instead of trapping. The call also previews KubeCon EU 2025, walks through wasmCloud's new auto-generated release notes driven by conventional commits, and covers community questions on built-in providers, wasi:http, and a community-built Cron capability provider.
Robust Rollouts & Rollbacks for the Wasm Component Model
The February 19, 2025 wasmCloud community call is a deep dive into how the platform should roll out and roll back Wasm component model applications in production. Brooks Townsend walks through a large RFC for robust, zero-downtime upgrades: reporting component and provider status in the host inventory, shifting lattice-wide state writes out of individual hosts and into wadm via a new control interface, and making provider configuration a request/response operation so the host actually knows whether a rollout succeeded. The discussion ranges from CI and license-compliance housekeeping through to where canary and blue-green deployments fit — and whether the host should grow a Kubernetes-style extension model.