Community Calls
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.
Debugging a wadm Component Update: Image References & the Component Model
The August 6, 2025 wasmCloud community call turned into a live debugging session around the Wasm component model in production. Mike, who runs a pipeline platform on wasmCloud, walked through what looked like either a misunderstanding or a bug: when he updated one of his deployed components to a new OCI image reference, wadm scaled the component but kept the old image — and, more worryingly, dropped the component's config. Brooks Townsend reproduced the issue alongside him, traced it to an incomplete diff in wadm's upgrade logic, and showed how to use NATS key-value buckets and event subscriptions to debug the running system.
wash OAuth Plugin & the Wasm Component Model Plugin System
The July 30, 2025 wasmCloud community call shows off the Wasm component model as a plugin system. Brooks Townsend demos an OAuth plugin for the wash CLI — a TinyGo WebAssembly component that runs a full OAuth login flow, stores credentials, and stays sandboxed in its own little file system — then lays out the migration path that takes the next-generation Wasm Shell into the wasmCloud org. Along the way the team agrees to ship the current wash as 1.0, call a feature freeze, surface a batch of good first issues, and check in on the Q3 roadmap, including the move to wRPC-based capability providers. Oh, and wasmCloud just passed 2,000 GitHub stars.
wash GitHub Actions & a Plugin System Built on Wasm Components
The July 23, 2025 wasmCloud community call is a developer-tooling deep dive built around Wasm components. Bailey Hayes walks through her exploration of GitHub Actions for the reimagined wash CLI — demoing a setup-wash-action, comparing composite, TypeScript, and Docker action styles, and digging into caching and CI supply-chain security. Brooks Townsend then shows the new wash plugin system, where every plugin is a WebAssembly component, and demonstrates how clap integration gives plugins native subcommands, flags, and environment variables. The group closes on how to trust third-party plugins by leaning on the Wasm sandbox and capability-based security.
wash: The Wasm Shell — a Plugin-Driven Wasm Component CLI
The July 16, 2025 wasmCloud community call is a ground-up rewrite of wash — "the Wasm Shell" — into a lean, plugin-driven CLI focused purely on Wasm component model development: build, run a dev loop, and push to an OCI registry, with everything wasmCloud-specific moving out into WebAssembly-component plugins. Brooks Townsend demos building and running components with no wasmcloud.toml, implementing a draft WASI interface with a component plugin, and hooking the dev loop with an Aspire dashboard plugin. The call closes with Eric Gregory's Q3 2025 roadmap recap, an issue of the week, and a new community Excalidraw room for diagrams.