Fiber VS Echo

Let's start the implementation using Fiber. First of all, you need to install Fiber.

I've been using a https://gofiber.io/ server setup to serve reactjs assets and provide an underlying API in the same container (mostly for proxying server to server authenticated requests)

I use Fiber. It's pretty good, simple, based on middlewares.

Something worth to look at: Fiber - An Express-inspired web framework written in Go.

Use https://github.com/gofiber/fiber and store the data in memory, and you can probably build this in an hour or two. The standard library HTTP is a bit more cumbersome, but there are plenty of tutorials for it too.

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