spin
design
spin | design | |
---|---|---|
22 | 34 | |
4,872 | 11,350 | |
2.8% | 0.2% | |
9.8 | 3.9 | |
2 days ago | 12 days ago | |
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.
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
design
-
Rust, WASM, and LOK
First of all, a quick rundown of what WASM is. It stands for Web Assembly. In essence, similar to how Java compiles down to a bytecode that is interpreted by a Java Virtual Machine, Web Assembly is a different bytecode interpreted by the browser. Many different languages can compile into WASM, and Javascript can interface with it like a module. In my case, I wrote a lot of the source code in Rust and compiled it down to a WASM module, then called into it from Javascript.
-
Surprisingly Powerful – Serverless WASM with Rust Article 1
WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable compilation target for programming languages, enabling deployment on the web for client and server applications. - https://webassembly.org
-
Reaching and surpassing the limits of JavaScript BigData with WebAssembly
With WebAssembly we can compile our C++ codebase into a wasm module for the browser. So when you look at a SciChart.js chart you're actually seeing our C++ graphics engine wrapped for JavaScript.
-
WASM Instructions
I should add, however, that the unmentioned elephant in the room is V8 JIT (TurboFan), which simply doesn't handle irreducible control flow. While there are some valid theoretical arguments around the current arrangement in Wasm, looking at the history of the associated discussions makes it pretty obvious that having V8 support Wasm and generate fast code similar to what it can do for asm.js was an overriding concern in many cases. And Google straight up said that if Wasm has ICF, they will not bother supporting such cases, so it will be done by a much slower fallback:
https://github.com/WebAssembly/design/issues/796#issuecommen...
AFAIK no other Wasm implementation has the same constraint - the rest generally tend to desugar everything to jumps and then proceed from there. So this is, at least to some extent, yet another case of a large company effectively forcing an open standard to be more convenient for them specifically.
-
Supercharge Web AI Model Testing: WebGPU, WebGL, and Headless Chrome
https://github.com/WebAssembly/design/issues/1397
> Currently allocating more than ~300MB of memory is not reliable on Chrome on Android without resorting to Chrome-specific workarounds, nor in Safari on iOS.
That's about allocating CPU memory but the GPU memory situation is similar.
-
Build your own WebAssembly Compiler
As far as I can tell (5 minutes of internet research) this was to allow easier compilation to JavaScript as a fallback in the days when WASM wasn't widely supported.
"Please add goto" issue has been open since 2016:
https://github.com/WebAssembly/design/issues/796
Most interesting comment:
> The upcoming Go 1.11 release will have experimental support for WebAssembly. This will include full support for all of Go's features, including goroutines, channels, etc. However, the performance of the generated WebAssembly is currently not that good.
> This is mainly because of the missing goto instruction. Without the goto instruction we had to resort to using a toplevel loop and jump table in every function. Using the relooper algorithm is not an option for us, because when switching between goroutines we need to be able to resume execution at different points of a function. The relooper can not help with this, only a goto instruction can.
> It is awesome that WebAssembly got to the point where it can support a language like Go. But to be truly the assembly of the web, WebAssembly should be equally powerful as other assembly languages. Go has an advanced compiler which is able to emit very efficient assembly for a number of other platforms. This is why I would like to argue that it is mainly a limitation of WebAssembly and not of the Go compiler that it is not possible to also use this compiler to emit efficient assembly for the web.
^ https://github.com/WebAssembly/design/issues/796#issuecommen...
-
Flawless – Durable execution engine for Rust
When I implemented a WASM compiler, the only source of float-based non-determinism I found was in the exact byte representation of NaN. Floating point math is deterministic. See https://webassembly.org/docs/faq/#why-is-there-no-fast-math-... and https://github.com/WebAssembly/design/blob/main/Nondetermini....
-
Requiem for a Stringref
> To work with GC, you need some way to track if the GC'd object is accessible in WASM itself.
I've never heard of a GC with that kind of API. Usually any native code that holds a GC reference would either mark that reference as a root explicitly (eg. https://github.com/WebAssembly/design/issues/1459) or ensure that it can be traced from a parent object. Either way, this should prevent collection of the object. I agree that explicitly checking whether a GC'd object has been freed would not make any sense.
> The reason why you probably need a custom string type is so you can actually embed string literals without relying on interop with the environment.
WASM already has ways of embedding flat string data. This can be materialized into GC/heap objects at module startup. This must happen in some form anyway, as all GC-able objects must be registered with the GC upon creation, for them to be discoverable as candidates for collection.
Overall I still don't understand the issue. There is so much prior art for these patterns in native extensions for Python, PHP, Ruby, etc.
-
The Tug-of-War over Server-Side WebAssembly
Giving you a buffer that grows is the allocation approach I am talking about. This is not how your OS works. Your OS itself works with an allocator that does a pretty good job making sure that your memory ends up not fragmented. Because WASM is in between, the OS is not in control of the memory, and instead the browser is. The browser implementation of "bring your own allocator" is cute but realistically just a waste of time for everybody who wants to deploy a wasm app because whatever allocator you bring is crippled by the overarching allocator of the browser messing everything up.
It seems like the vendors are recognizing this though, with firefox now having a discard function aparently!
https://github.com/WebAssembly/design/issues/1397
- How do Rust WebAssembly apps free unused memory?
What are some alternatives?
wasmCloud - wasmCloud allows for simple, secure, distributed application development using WebAssembly components and capability providers.
content - The content behind MDN Web Docs
lunatic - Lunatic is an Erlang-inspired runtime for WebAssembly
wave - Realtime Web Apps and Dashboards for Python and R
wit-bindgen - A language binding generator for WebAssembly interface types
interface-types
component-model - Repository for design and specification of the Component Model
Chevrotain - Parser Building Toolkit for JavaScript
distribution-spec - OCI Distribution Specification
WASI - WebAssembly System Interface
spec - WebAssembly for Proxies (ABI specification)
iswasmfast - Performance comparison of WebAssembly, C++ Addon, and native implementations of various algorithms in Node.js.