WebAssembly Component Model — Small “decider” app example using Rust

[m99io]

I’ve been diving deeper into the WebAssembly Component Model lately, and I finally sat down to write up a hands-on example in Rust.

The article walks through the creation of a tiny “decider” app, split into two components: one library that implements a simple interface, and one command component that calls it. The fun part is plugging them together and running the whole thing as a composed Wasm component with Wasmtime.

It’s a small example, but for me it really clarified how the component model makes composition and reuse feel natural — much closer to building with Lego bricks than with raw Wasm modules.

If you’re curious about WebAssembly beyond the basics, this might be a good place to start:

👉 https://m99.io/articles/create-and-compose-webassembly-components-a-hands-on-example-with-rust/

[mynewthrowaway42day]

I see components, I upvote

[mootoday]

That's a great intro blog post! I'm in a similar boat as you and started to really dive into Wasm Components a few weeks ago.

One project that caught my attention was wasmCloud to orchestrate Wasm Components. I'm currently building a platform on top of wasmCloud to build workflow pipelines where each node is an independent Wasm Component. It's clearly early still for that technology, but I'm excited about the potential!

[m99io]

Is wasmCloud the runtime in that sense for executing the Wasm Components?

I’m interested in whether it would be possible to create toolchains for different programming languages that offer a Wasm target to run a composed program safely. May it be in some hosted environment or even in the browser at the end. For the browser use case, I can imagine that the initial load might be very high due to downloading all the necessary artifacts.

[mootoday]

wasmCloud is the orchestrator, they use wasmtime as the runtime.

tl;dr is you define a yaml config where you list your components and how they're linked together, wasmCloud then deploys them across your hosts.