athens VS httprouter

I wrote this a few years ago. This is the basic way to do it. A better developer experience is to set up an Athens proxy and use Go environment variables to tell the tool chain where to look for modules.

(found a similar open issue 2.5yr old on Athens)

For the proxy I used Athens. https://docs.gomods.io

Athens, a self-hosted free Go proxy implementation, implements rate-limiting for GitHub (with a pretty horrific Github-specific behavior). This means GitHub does implement rate-limiting to cope with aggressive Go proxies.

https://github.com/gomods/athens/blob/723c06bd8c13cc7bd238e6...

Food for thoughts.

[1] https://github.com/gomods/athens

Following the completion of the series — Secure and performant full-stack authentication system using rust (actix-web) and sveltekit and Secure and performant full-stack authentication system using Python (Django) and SvelteKit — I felt I should keep the streak by building an equivalent system in PURE go with very minimal external dependencies. We won't use any fancy web framework apart from httprouter and other basic dependencies including a database driver (pq), and redis client. As usual, we'll be using SvelteKit at the front end, favouring JSDoc instead of TypeScript. The combination is ecstatic!

Gin is a web framework written in Go. It features a martini-like API with performance that is up to 40 times faster thanks to httprouter. If you need performance and good productivity, you will love Gin.

But, if you care about speed take a look at httprouter. That's the one we're using in our company. It's fast but the biggest downsides for me are:

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。

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/