containerd-wasm-shims
spin
containerd-wasm-shims | spin | |
---|---|---|
4 | 22 | |
293 | 4,913 | |
3.4% | 3.6% | |
8.1 | 9.8 | |
about 1 month ago | 8 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
containerd-wasm-shims
-
Spin 1.0 — The Developer Tool for Serverless WebAssembly
Besides deploying the application locally and deploying to Fermyon Cloud, you can also deploy your Spin application to Kubernetes using the new Containerd integration for Spin.
-
Why did the Krustlet project die?
Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did it - you'd have kubelet/containerd nodes and krustlet/wasm nodes, and could only run the appropriate workload on each node type.
-
New Docker Desktop: Run WASM Applications Alongside Linux Containers in Docker
You can absolutely install the wasm shim without Desktop. (They won't tell you that because Desktop is a revenue stream for Mirantis.)
In your VM or WSL instance that's running Docker, get the shim from here: https://github.com/deislabs/containerd-wasm-shims (You might need to build it yourself)
Then specify the --runtime and --platform arguments like instructed in the doc, but with a slight modification:
--runtime=containerd-wasm-shim=/path/to/containerd/wasm/shim
This works because the container runtime is simply a Go binary, and Go binaries are completely self-contained.
spin
-
Git Prom! My Favorite Git Alias
For example, here's a snippet of my Git config for the spin repository:
-
4 Ways to Participate in Advent of Spin - A Wasm Coding Challenge
We built (and open-sourced) Spin to make the developer experience easier, and we want to show you this through Fermyon's Advent of Spin. You will be presented with fun coding challenges that'll help you learn to build with Spin and WebAssembly.
-
Creating a Server Side Rust WebAssembly App with Spin 2.0
Fermyon Spin is the open source tool for building serverless functions with WebAssembly. We’re going to use a few Spin commands to go from blinking cursor to deployed app in just a few minutes. Along the way, we’ll walk through a Spin project and see some of the features of Spin 2.0.
-
Flawless – Durable execution engine for Rust
linky: https://github.com/fermyon/spin#readme (Apache 2; and while I don't see any CLA, interestingly they do require GPG signed commits: https://developer.fermyon.com/spin/contributing-spin#committ... )
-
Building microservices in Rust with Spin
To install the binary file on Windows, download the Windows binary release, unzip the file, and place the spin.exe file in your system path.
-
Spin 1.0 — The Developer Tool for Serverless WebAssembly
We are delighted to introduce Spin 1.0, the first stable release of the open source developer tool for building serverless applications with WebAssembly (Wasm)! Since we first introduced Spin last year, we have been hard at work together with the community on building a frictionless developer experience for building and running serverless applications with Wasm.
- Spin – Build Microservices with WebAssembly
-
Waggy v0.3 Released!!
“Waggy is used for writing WAGI (WebAssembly Gateway Interface) compliant API routers/individual handlers. WAGI was developed by deislabs for accepting and routing incoming HTTP requests with WebAssembly via a configuration file (modules.toml) defining routes, modules, volumes to be mounted, etc. WAGI can run as a stand alone server, or with a framework such as the Fermyon/Spin framework Go SDK. Waggy allows for the flexibility of handling the routing via the modules.toml, or to define it code (Waggy is written in Go), as well as various pieces of convenient functionality such as the new features described above!!”
-
WasmEdge
They’re VC-funded and will vendor lock-in you. See their response to my discussion:
https://github.com/fermyon/spin/discussions/861
With WasmEdge there is no vendor lock-in, it’s opaque and standards-based
-
Recommendations for a resource efficient backend framework?
What language do you want? And how experimental are you wanting to go? This project is crazy cool https://github.com/fermyon/spin , but might be harder to work with if you’re not willing to use rust :p, think they might have made it easy for c# too though
What are some alternatives?
krustlet - Kubernetes Rust Kubelet
wasmCloud - wasmCloud allows for simple, secure, distributed application development using WebAssembly components and capability providers.
spin-plugin-k8s - A Kubernetes Plugin for Fermyon Spin
lunatic - Lunatic is an Erlang-inspired runtime for WebAssembly
spin-fileserver - A static file server implemented as a Spin component
wit-bindgen - A language binding generator for WebAssembly interface types
runwasi - Implementation for runs wasm workloads in Wasmedge
component-model - Repository for design and specification of the Component Model
preview2-prototyping - Polyfill adapter for preview1-using wasm modules to call preview2 functions.
distribution-spec - OCI Distribution Specification
Podman Desktop - Podman Desktop - A graphical tool for developing on containers and Kubernetes
spec - WebAssembly for Proxies (ABI specification)