Echo VS httprouter

i prefer echo https://echo.labstack.com/ but from these two, i'd choose fiber

labstack/echo

Echo

I use https://echo.labstack.com/, it's minimalist. Pocketbase also uses Echo.

2. echo. Golang's echo framework is a high-performance, extensible, and simple web framework. It intelligently prioritizes routes and has a highly optimized HTTP router with no dynamic memory allocation. It is used to create dependable, scalable, and easily segmentable REST APIs. It supports HTTP/2, which increases speed and offers a better user experience, and automatically installs TLS certificates from Let's Encrypt. Additionally, there are numerous built-in middlewares available for use, and programmers can even create their own custom middlewares that can be set at the root, group, or route level. The echo framework's disadvantage is that there is just one developer who maintains it, and there aren't many updates to the code. Documentation Link: https://github.com/labstack/echo

Hertz was inspired by other open-source frameworks like fasthttp, gin, and echo, in combination with unique challenges faced by ByteDance, Hertz has become production ready and powered ByteDance’s internal services over the years.

This is thread from Echo github discussions "Is Echo is more efficient than Gin?" https://github.com/labstack/echo/discussions/2143

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.

May I suggest using this httprouter for router and this for middleware Alice

Minimal dependencies: julienschmidt/httprouter and goccy/go-json

The biggest shortcomings of the default net/http implementation are, in my opinion, the inability to route based on HTTP method and the lack of path-based parameters. That being said, a full framework is often overkill as well. I'd probably recommend something like Gin or Chi, or even just httprouter if you want to be really minimal.