Fiber VS mux

⭐ Fiber on GitHub (35k+ stars)

While researching, I found samples using Gin in the official AWS Lambda Web Adapter examples and a Zenn article with a Fiber sample. However, I couldn’t find any samples using Echo, so I decided to publish this article.

Fiber

When creating this template project, I saw that I had to set up the server manually and I used gofiber as it has express-like functionalities, and as a MERN stack developer, I found it very easy to use. Once I thought to make a server-project generator in Express as well, but they already have one, it is called express-generator. Then I thought there might be the same thing for Fiber as well. But when I searched in GitHub with the topic:go-backend-template, I only found pre-made templates that you can clone and use for your projects. That's when I decided to give it a shot.

Go Fiber has a growing developer and user base. With over 31k stars on GitHub, you can tell that it’s constantly updated and maintained by a devoted team of contributors. You can also raise issues, ask questions, and participate freely thanks to the supportive community.

To make my life easier, I added Fiber, a popular lightweight framework. Regardless of which package you use, the process and most of the code will remain unchanged.

Since you're from Nodejs just like me, I use fiber https://gofiber.io/ it's easier to understand from a Nodejs background (express, etc) and there's nothing wrong using it if you know it, your casual application wont need all the performance in the world Go provides

I think u should try Fiber it's the fastest according to the benchmarks and imo it's the best I love it!!!

Boneless is a powerful tool that offers a wide range of features to facilitate application development. In this blog post, we will explore some essential tools that can be used in conjunction with Boneless: Service Weaver, Go Migrate, SQLC, and Fiber. Let's discover how these tools can boost productivity and efficiency in application development.

Very cool about the SEA feature, I haven't seen that before. Thanks for sharing that

This is sort of the worst case comparison, but a hello world program in go is 1.5 MiB and the SEA node equivalent is 109 MiB. Obviously as your program becomes more complex that fixed overhead becomes less of an issue but I think it's still a useful comparison.

For the packages, the thing I prefer even more so is writing an application with 0 dependencies at all. net/http, net/http/pprof, flag, pprof, etc are all built in and high quality and you can easily build clis/servers with them. Even a really full featured CLI builder package like cobra has just a few transitive deps and gorilla/mux has none: https://github.com/spf13/cobra/blob/main/go.sum https://github.com/gorilla/mux/blob/main/go.mod

If I compare that with express.js or commander its a very different story (though, in fairness to commander, they all seem to be dev deps).

I don't think it's bad per se to have deps, just a different culture. https://news.ycombinator.com/item?id=43935067 kinda beat that horse already though

Given my experience with Go, I asked Claude 3.7 Sonnet to create all the backend API routes and logic using Go and the Gorilla Mux framework. 🚀 This allowed me to leverage my existing knowledge and skills while still benefiting from the efficiency and accuracy of vibe coding.

For routing, we will be using the Gorilla Mux routing library, but feel free to use any routing solution of your choice. We will also be using Google’s UUID library for Go to generate random names for our files when we upload them. This is a personal preference as you can generate file names in different ways.

We also need to install the Gorilla Mux Router which will be the routing library for our project. Run the two commands below at the root of your project to get these libraries installed into your project

This is not a disproval, but gorilla/mux has comparatively poor benchmark results among popular (many stars) third-party HTTP routers. , used by many users.

This attention to detail also can mean that for key abstractions in a tool or framework, what concretely goes on doesn't go unexplained. For example, when I was learning Go for web development, my first stumbling block was understanding how interfaces worked, particularly http.Handler, which is key to doing web development with Go's powerful net/http package and the fits-like-a-glove package built on top of it, the Gorilla Mux router. My way of finding out how that worked, and seeing the elegance of that interface, was pretty unorthodox - I figured out how Handlers worked by looking directly at Go's source code (which also is a demonstration of Go's readability, if you're interested in joining the Gophers!). And coming out of that was my very first tech talk at in 2015, on learning Gorilla from its Node.js counterpart, Express.js!

In this ApiGateway implementation, we've employed the Gorilla Mux router for enhanced route handling. Let's break down the key components: