wasmCloud VS axum-aws-lambda

There’s a lot more to go into there, but you may find https://wasmcloud.dev interesting 🙂

The wasmCloud project (https://wasmcloud.dev) has a number of areas where people can contribute. As someone else said, you can filter on "good first issue" to get an idea for what needs doing.

Webassembly is also gaining steam for server workloads due to several advantages (less overhead, better capability based security, composability, ...).

See Spin [1], Wasmcloud [2], Lunatic [3], etc.

My system is based on a distributed Webassembly runtime.

The reason for taking inspiration from Kubernetes is making deployment of distributed workloads on that runtime easy.

A nice benefit for a Kubernetes alike system is that the equivalent to controllers can be much more light-weight WASM actors that are easier to deploy and scale.

[1] https://github.com/fermyon/spin

[2] https://github.com/wasmCloud/wasmCloud

[3] https://github.com/lunatic-solutions/lunatic

If you are developing a HTTP web app i recommend Axum and https://crates.io/crates/axum-aws-lambda. It lets you run your app as a standard web app anywhere (good for local dev/testing) and also run using the aws-lambda-rust runtime with no code changes. The other advantage is you get a bunch of middleware available for free like CORS, compression etc.

I put together a crate that exports a shim tower::Layer between axum and the lambda runtime: enabling you to switch between running a local server for debugging and compiling for AWS Lambda.