This folder contains examples of projects you can run with wasmCloud.
Before you can run these examples, you'll need the wasmCloud Shell (wash) installed on your machine.
wash is used for both starting a new host (wash up) and performing actions on an existing host like starting a workload (WebAssembly components or capability providers).
Most examples will use wasmCloud Application Deployment Manager (wadm), which is built into wash to declaratively launch workloads. Usually, you'll be running wash app deploy path/to/wadm.yaml.
wasmCloud runs WebAssembly Components. Write business logic in your favorite $LANGUAGE, compile to WebAssembly, and deploy your code to hosts on a local or remote wasmCloud lattices.
Want to write some code that responds to web requests, talks to a database and does some logging? That's a WebAssembly component.
You can get started quickly by trying out of our example projects:
| Language | Where you should start | OCI Artifact |
|---|---|---|
| Golang (TinyGo) | ./golang/components/http-hello-world |
|
| Golang (TinyGo) | ./golang/components/http-echo-tinygo |
|
| Python | ./python/components/http-hello-world |
|
| Rust | ./rust/components/echo-messaging |
ghcr.io/wasmcloud/components/echo-messaging-rust:0.1.0 |
| Rust | ./rust/components/blobby |
ghcr.io/wasmcloud/components/blobby-rust:0.4.0 |
| Rust | ./rust/components/http-hello-world |
ghcr.io/wasmcloud/components/http-hello-world-rust:0.1.0 |
| Rust | ./rust/components/http-jsonify |
ghcr.io/wasmcloud/components/http-jsonify-rust:0.1.1 |
| Rust | ./rust/components/http-keyvalue-counter |
ghcr.io/wasmcloud/components/http-keyvalue-counter-rust:0.1.0 |
Start components with wash, either from file or OCI reference (if available):
wash start component file:///path/to/examples/project/build/name_of_component_s.wasm component
wash start component ghcr.io/wasmcloud/components/http-jsonify-rust:0.1.1 http-jsonfiyWarning
Not all WebAssembly component examples have officially maintained OCI artifacts.
Want to use a component from your own registry? After wash building your component, wash push it to your registry of choice.
wasmCloud runs capability providers which are binaries that "provide" stateful and/or advanced functionality to the rest of the wasmCloud lattice. While components contain high level business logic and are quite light, providers normally contain more low level implementation that components rely on.
Want to implement an interface for reading and writing key-value data that speaks to a real database? That's a wasmCloud provider.
wasmCloud capability providers run as child processes on the wasmCloud host, and are mostly unrestricted, meaning you don't have to wait for WebAssembly ecosystem support for your code -- whatever advanced functionality (connecting to databases, AI/ML, raw hardware access, proprietary software, etc) you can build into a regular binary today can exposed for WebAssembly components running on your lattice to consume.
You can get started quickly by trying out of our example projects:
| Language | Folder | OCI Artifact |
|---|---|---|
| Rust | ./rust/providers/messaging-nats |
Warning
Most wasmCloud example providers do not have officially maintained OCI artifacts.
Want to use a provider from your own registry? Build a Provider ARchive (PAR) file with wash par and wash push it to your registry of choice.