mux VS httprouter

We will be using Gorilla Mux to create the APIs locally. Gorilla Mux implements a request router and dispatcher to match the incoming requests.

https://github.com/gorilla/mux/issues/659 Don't get me wrong, I appreciate the good intentions but why didn't you become a maintainer of the original project?

gorilla/mux

popular libraries looking for new maintainers and getting eventually archived ( https://github.com/gorilla/mux )

From the devs:

Initially found out about this via this issue thread here where they were looking for new maintainers.

The maintainer of Gorilla is in the process of dropping the project (he just doesn’t have enough time for it anymore) and is looking for new maintainers. A number of volunteers have replied to the issue but it seems like nobody has been chosen yet even though the call for new maintainers has been up for over a year.

According to maintainer requirements provided here, it's pretty obvious that it's quite hard to find new maintainers.

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

Also, you seemed to have copied the path.go from Julien Schmidt's httprouter without even thanking or mentioning it in the README, which I think is not a good attitude. Yes, httprouter is BSD-3-Clause licensed, but showing the people that you took the code from some respect, should be a absolute must, in my opinon.

For a simple web app, https://github.com/julienschmidt/httprouter

Take this as the high-performing router (I used this in an early demo for the company I worked for when we considered Golang). https://github.com/julienschmidt/httprouter/blob/34250257ea144905c752bfaae80d6885f190daf6/tree.go

The julienschmidt/go-http-routing-benchmark is the julienschmidt/httprouter, but maintenance seemed to have stopped in recent years, so I decided to create my own benchmarker and implement it. I decided to implement bench markers.

As another aside, I will actively discourage Iris. https://github.com/julienschmidt/httprouter/issues/148 https://www.reddit.com/r/golang/comments/b481q7/a_warning_about_githubcomkatarasiris/

Add NewHttpRouterSrv api for using httprouter (which is used by gin) as router

I'll check (and I extensively use) httprouter along the stdlib.

I prefer to use either https://github.com/gin-gonic/gin, vanilla go http handlers around https://github.com/julienschmidt/httprouter, or wrap the forementioned http router with a extension that allows my handlers to return errors and/or response models.

Agreed, but I now use this httprouter pkg in every Go webservice project now. It's one of only a few third-party dependencies for most of my Go projects too because of how bountiful the stdlib is.