Community Calls
Building an ETL Pipeline from Wasm Components on wasmCloud
The June 11, 2025 wasmCloud community call opens with a fast-turnaround demo from Mike Nikles, who in seven days went from boxes on a whiteboard to a working drag-and-drop ETL pipeline builder running on wasmCloud. Each pipeline stage is a Wasm component — composed with wac, deployed as a wadm manifest, and wired together over NATS messaging. The discussion that follows digs into composing components statically vs. linking them dynamically with wRPC, the case for WASI P3 streams, and HTTP/2 support for agentic protocols. Brooks Townsend then kicks off the Q3 2025 roadmap planning and walks through a new consolidated NATS reference doc.
ETL Pipelines on the Wasm Component Model with wasmCloud
The June 4, 2025 wasmCloud community call is a design review for a data-processing platform built on the Wasm component model. Mike Nikles walks through an architecture diagram for a drag-and-drop ETL pipeline platform built on wasmCloud, where each pipeline step composes trusted in/out components around an untrusted customer-authored business-logic component. Brooks Townsend recognizes the design as wasmCloud's platform harness pattern, and the group works through capability providers, HTTP-server density, and lattice-per-customer versus lattice-per-pipeline isolation. With many maintainers at a Cosmonic off-site doing roadmapping, this is a lighter, feedback-focused call.
Testing Wasm Component Model Functions with wasmtime run
The May 28, 2025 wasmCloud community call is a short, hands-on session about testing Wasm component model functions. Brooks Townsend demos wasmtime run --invoke — a new flag in Wasmtime 33 that calls any exported function on a WebAssembly component directly from the command line, passing strongly typed arguments via the WebAssembly Value Encoding (WAVE) syntax. That sparks a discussion about bringing the same ergonomics to wasmCloud's wash call. The team then reviews the Q2 2025 roadmap, and Florian Fürstenberg presents a detailed investigation into why an overloaded Hello World component can deadlock the whole application — tracing it to wRPC handshakes, NATS subscriptions, and the host's invocation semaphore.
A Year of wasmCloud 1.0: WASI, the Wasm Component Model & 2.0
The May 21, 2025 wasmCloud community call is a short, reflective one centered on the Wasm component model and the standards beneath it. Brooks Townsend walks through his new blog post celebrating a year of wasmCloud 1.0 — built on WASI 0.2, WIT, and the component model — and the deliberate bet on WebAssembly standards that drove community growth. Taylor Thomas and Liam Randall look ahead to wasmCloud 2.0, WASI 0.3, and a more pluggable host shaped by user design feedback. The call closes with an Issue of the Week and a Documentation of the Week highlighting a new capability-provider icon.
wRPC Error Handling & axios in a Wasm Component Model App
The May 14, 2025 wasmCloud community call brings back the "Documentation of the Week" and "Issue of the Week" segments and digs into two practical threads in the Wasm component model. Brooks Townsend walks through the experimental error handling for custom interfaces landed in wasmCloud 1.8 — where wRPC surfaces platform-level transport errors to the guest instead of panicking — and turns the gap in its docs into an Issue of the Week. Victor Adossi then demos a new TypeScript example that runs the popular axios HTTP library inside a WebAssembly component, and the team gives kudos for a new cron job capability provider and per-component memory limits.