waggy
recipes
waggy | recipes | |
---|---|---|
8 | 17 | |
38 | 2,876 | |
- | 1.2% | |
3.0 | 9.7 | |
about 1 year ago | 4 days ago | |
Go | Go | |
BSD 3-clause "New" or "Revised" License | MIT License |
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
recipes
- Fiber – Express inspired web framework written in Go
-
go-mir - a toolkit to develop RESTful API backend service like develop service of gRPC
Mir is a toolkit to develop RESTful API backend service like develop service of gRPC. It adapt some HTTP framework sush as Gin, Chi, Hertz, Echo, Iris, Fiber, Macaron, Mux, httprouter。
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
-
I know JavaScript and looking for Go learning resource
With lovely recipes: https://github.com/gofiber/recipes
-
The best Go framework: no framework? (Three Dots Tech)
If I started working at a Go shop that used a framework, I would hope it would be Fiber. Not for any particular solid reasons, though. Rather just personal preference based on how the developer experience feels to me personally.
- Criando uma API Rest com Fiber - Uma história pessoal de aprendizado
- Construindo uma API organizadinha em Golang usando Fiber
- Lightweight opensource Go-based spa-to-http tool "beats" Nginx in SPA serving performance
-
Ask HN: What GO web framework do you use?
I use Fiber [0] in production for a $4M ARR company and never had any issues.
Took less than a month to start with and integrate and it is a joy to use.
[0] https://github.com/gofiber/fiber
-
Framework or advices for API
Fiber is quite light weight and performant, its beginner friendly as well. The complexity of your app has to live somewhere. You are going to need a router at least, any framework that is lightweight and has sensible defaults is always worth considering over doing everything on your own. There are plenty of useful examples
What are some alternatives?
gorilla-mux - A fork of gorilla/mux, the powerful HTTP router and URL matcher for building Go web servers with 🦍
go-clean-arch - Go (Golang) Clean Architecture based on Reading Uncle Bob's Clean Architecture
httprouter - A high performance HTTP request router that scales well
fiber-go-template - 📝 Production-ready backend template with Fiber Go Web Framework for Create Go App CLI.
jwtauth - JWT authentication middleware for Go HTTP services
oapi-codegen - Generate Go client and server boilerplate from OpenAPI 3 specifications
otelchi - OpenTelemetry instrumentation for go-chi/chi
imgui-go-examples - Examples of Dear ImGui for Go
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
fiber-versioning-boilerplate - A boilerplate for fiber versioning, Clean Architecture, API versioning, API documentation, Data versioning
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍
tutorial-go-fiber-rest-api - 📖 Build a RESTful API on Go: Fiber, PostgreSQL, JWT and Swagger docs in isolated Docker containers.