restruct VS waggy

For me it's mux and my personal router restruct but since mux is not maintained anymore, maybe chi will be my goto for new projects that needs more stability in the api. Since restruct is a router based on structs, which I use for fast prototyping.

Not the best, but after using gorilla mux for routing for a while, I've decided to build my own https://github.com/altlimit/restruct

I've always just use gorilla mux and try to stay close to standard handlers as much as possible and code my request response process. As I've done this multiple times and actually been doing things over and over again I've developed my own router based on structs. Most of the time I develop something that's not going to be public api so I just want to easily build endpoints from struct method without defining new routes. I made https://github.com/altlimit/restruct for it. I also made it flexible so it can do a good amount of routing config. Then with same idea on authentication I made gauth. It's under the same org of that repository. Just to make my development for clients faster while sticking close to standards. I can't find myself using those frameworks that keeps introducing their own context somehow. I did use them before but somehow just doesn't feel right.

github.com/altlimit/restruct

Chi for work, my own router for personal projects

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.

For work, we’ve switched to Chi. For personal projects, I use a router I’ve been built and have been working on myself

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 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 has released v2!!

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.