Community Calls
Wasm Component Model: Plugins, Shared Memory & WASI 0.3
The September 10, 2025 wasmCloud community call started as "the quickest wasmCloud Wednesday ever" — no agenda, with the team heads-down on the last items of the Q3 roadmap — and then turned into a wide-ranging hallway conversation about the hard edges of the Wasm component model. Brooks Townsend, Colin Murphy, and Victor Adossi dig into why adding system time-zone support to Wasmtime takes a year and a half, how a wasmCloud host plugin could route around runtime bottlenecks, Christophe's shared-memory proof of concept, and why first-class functions in WIT are the missing piece for generating polyglot SDKs — all while looking ahead to what WASI 0.3 (Preview 3) unlocks.
In-Process Component Calls & the Wasm Component Model
The September 3, 2025 wasmCloud community call digs into the Wasm component model as the foundation for a leaner, more modular runtime. Brooks Townsend walks through in-process component-to-component calls — letting two components on the same host talk directly instead of going over wRPC/NATS, dropping latency from hundreds of microseconds to single-digit nanoseconds — and a broader effort to shrink the wasmCloud host's responsibility down to component lifecycle management, with capabilities provided through an optional plugin layer. Bailey Hayes closes with a quick demo of new shell auto-completions in the wash CLI.
Wasm Component Model vs Capability Providers & the wash Plugin System
The August 27, 2025 wasmCloud community call digs into how the Wasm component model is reshaping wasmCloud's architecture. Brooks Townsend tours the new wash plugin system — hooks, dev register plugins, and top-level commands, all powered by WebAssembly components — and opens a Q3 roadmap discussion with maintainer Aditya on rethinking the application abstraction and increasing provider density. Brooks and Bailey Hayes make the case for leaning into wRPC over the capability-provider SDK and for letting components, with WASI P3 on the horizon, take over many jobs that native providers do today through bin packing, dynamic linking, and Cranelift optimizations.
wash 1.0 Beta: Wasm Component Model Plugins & Good First Issues
The August 20, 2025 wasmCloud community call is a quick, contributor-focused update centered on the new wash 1.0 beta — a greenfield "Wasm Shell" whose plugins are themselves Wasm components, written in either Rust or Go. Brooks Townsend walks through Eric's fresh "good first issues" blog mapped to the Q3 2025 roadmap, highlights the setup-wash GitHub Action now headed for the Actions marketplace, and recaps the wasmCloud 1.9 minor release: XDG base-directory support, a dashboard for wash dev, and a new built-in HTTP client provider.
Event Sourcing with the Wasm Component Model & Resources
The August 13, 2025 wasmCloud community call is a deep conversation on the Wasm component model applied to event sourcing. Brooks Townsend walks through an experimental repo that models an entire event-sourcing system purely from the composability of WebAssembly components — command handlers, event handlers, an event sourcer, and an event store — using Wasm resources as opaque handles so the core system can pass commands and events around as bytes without knowing their structure. Yordis Prieto then shares his multi-year journey from Elixir event sourcing into WebAssembly, why he chases Wasm to control indeterminism, and the concrete WIT features (maps, structs, recursive types, generics) he is pushing for upstream — including a recent conversation with Luke Wagner.