Echo VS httprouter

This post will discuss building a user management application with Golang using the Echo framework and MongoDB. At the end of this tutorial, we will learn how to structure an Echo application, build a REST API and persist our data using MongoDB.

We usually look for web frameworks if we want to build REST APIs, in case of Golang, we have echo, gin, fibre, etc.

It's basically a simplified reverse-proxy configurable via a YAML file which redirects requests to the configured webhook URLs allowing you to host multiple Telegram bots in the same HTTP port. It uses Echo as the webserver.

https://echo.labstack.com is fantastic

Since I'm using echo as the web framework to control my decorations, I was able to implement some pretty simple middleware that rejects POST requests from IP addresses that aren't within close proximity to mine with a 403 status code.

For backend I'd say -> Golang, PostgreSQL, Redis. I've just worked with Vue.js but I've seen some of the React codebases and don't really appreciate that complexity. Vue does a far better job and simplifying things.

With Golang, you actually don't need a mega framework to get started, you can use small libraries that will do the job for you without doing any magic behind the scenes. (Like, for sure you can use echo[0] but you would probably be happy with mux[1] and it's middlewares itself). And it's not uncommon in Go codebases to repeat yourself. I'd argue that's a much better paradigm than polluting your codebase with 10k indirect dependencies, the garbage that is the Node.js ecosystem.

[0]: https://echo.labstack.com/

This can be extremely helpful if you just want to get going and start writing the business logic of your application without having to worry about some of these implementation details however it does come with a price: you're mostly stuck with the framework's choices. Don't like the way that echo formats logs? Tough. Want to use a different router than the one chosen by buffalo? Good Luck.

I tried once to only use the standard library for a REST-like api and ended removing all that code and replacing it with a framework (Echo in my case) once i noticed that all that those thousands lines of code that i wrote to handle errors, requests, responses, validations, etc were almost the same to the ones you could find it those frameworks.

Gin-gonic, popularly known as Gin, is an HTTP web framework written in Golang with performance and productivity support. Gin uses a custom version of HttpRouter, a lightweight, high-performance HTTP request router that navigates through API routes faster than most frameworks out there.

At work for a real-time bidding system in programmatic advertising we use https://github.com/julienschmidt/httprouter

I'm trying to set up the swagger using julien schmidt's HTTP router, but the setup returns a 404 Error Not Found every time. Anything that I'm missing out on here. Link to the router: https://github.com/julienschmidt/httprouter

As for the first question, see https://github.com/julienschmidt/httprouter/issues/73 and the lack of middlewares.

Pass on the frameworks at first. just use the std library's net/http package and maybe a really basic router like julien schmidt's httprouter(https://github.com/julienschmidt/httprouter) to do your requests and use pgx(https://github.com/jackc/pgx) for postrgres.

httprouter for routing. Several years ago (5 years ago maybe) when I started using Go, I always tried to use the best and fastest packages and this package boasts itself as the fastest router for Go. Fast forward to today, I'm not sure if it still the fastest around, but it's stable and I've never had issues with it, so I keep using it.

I use (and love) gorilla/mux as well as julienschmidt/httprouter. They are both on the "lightweight" end of the spectrum. Nothing (to my knowledge) beats the performance of julienschmidt/httprouter, but routing isn't going to be your main bottleneck anyway, so I don't think it matters too much. If you wanted to get started with gorilla, gowebexamples.com is a nice starting point.

For me, the middle ground is best, chi, gin, httprouter are the sweetspot. But that's based on skills, style, and requirements (and experience - I've used all the ones I have mentioned in anger)