waggy
spin
waggy | spin | |
---|---|---|
8 | 22 | |
38 | 4,872 | |
- | 2.8% | |
3.0 | 9.8 | |
about 1 year ago | 2 days ago | |
Go | Rust | |
BSD 3-clause "New" or "Revised" License | 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.
waggy
-
what's your recommended router? chi, mux, something else?
Chi for work, my own router for personal projects
-
Waggy hits v0.8.0 with support for custom middleware, listening and serving on a specific host and port address, and more!!
And in that time, I’ve gotten the router I’ve been working on, Waggy, up to a new version of v0.8.0!! Along with some minor bug fixes, some refactoring, and restructuring changes, there is now full support for custom middleware and listening and serving on a specific host:port address.
-
What mux/router to use now a days?
For work, we’ve switched to Chi. For personal projects, I use a router I’ve been built and have been working on myself
-
Gorilla Web Toolkit is now in archive only mode
I have a library that I’ve been working on for a different environment (WASM specifically), but I can be used as a regular HTTP router and provides access to URL path params. Check it out here
-
Waggy v0.3 Released!!
Waggy v0.3 is out now!! Along with some minor bug fixes, v0.3 comes with two major improvements, being the ability to configure loggers for WaggyRouters and WaggyHandlers alike, as well as a convenience wrapper for serving files as responses. One other big unplanned, but welcome improvement is the ability to use Waggy in conjunction with Fermyon’s Spin Go SDK for writing WAGI microservices that can also make outgoing HTTP calls.
-
Waggy v2 Release
Waggy has released v2!!
-
The best Go framework: no framework? (Three Dots Tech)
With the rising popularity of WASM, I’d probably use something like wazero coupled with the library I just wrote and released, waggy for writing the individual handlers for each route, though.
- Waggy: A dead simple library for writing WAGI API Handlers in Go
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?
gorilla-mux - A fork of gorilla/mux, the powerful HTTP router and URL matcher for building Go web servers with 🦍
wasmCloud - wasmCloud allows for simple, secure, distributed application development using WebAssembly components and capability providers.
httprouter - A high performance HTTP request router that scales well
lunatic - Lunatic is an Erlang-inspired runtime for WebAssembly
jwtauth - JWT authentication middleware for Go HTTP services
wit-bindgen - A language binding generator for WebAssembly interface types
otelchi - OpenTelemetry instrumentation for go-chi/chi
component-model - Repository for design and specification of the Component Model
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍
distribution-spec - OCI Distribution Specification
restruct - RESTruct is a rest router written in Go to automatically create routes based on your structs.
spec - WebAssembly for Proxies (ABI specification)