Echo VS mux

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.

https://echo.labstack.com is fantastic

For REST, I use Echo which bills itself as a Web Framework. So in that sense, yes. In the sense of something overarching like Java's Spring Framework, no.

It's looks exactly like Echo? Even the landing page is similar: https://echo.labstack.com/

It’s Echo itself that logs incoming requests. https://github.com/labstack/echo/issues/1017

In this article let's try to create closer to real world CQRS microservices with tracing and monitoring using: 🚀 Kafka as messages broker gRPC Go implementation of gRPC PostgreSQL as database Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus MongoDB Web and API based SMTP testing Redis Type-safe Redis client for Golang swag Swagger for Go Echo web framework

Eli Bendersky has an excellent series where they walk you through building a REST API in Go by first starting with the standard library and then introducing a router such as gorilla or chi and finally switching over to using a complete web framework. This series shows some of the downsides of sticking with the standard library entirely and how extra libraries such as the two router packages above can be extremely helpful.

gorilla/mux

I recommend gorilla/mux (https://github.com/gorilla/mux), a most widely used http router library and go-doudou (https://github.com/unionj-cloud/go-doudou) RESTful microservice framework based on it. Go-doudou supports developing monolith service as well. It's also a code generator cli which can generate main function, routes, http handlers, mock service implementation, http client, OpenAPI 3.0 json spec and more to let you deploy your awesome projects as soon as possible.

Routing: https://github.com/gorilla/mux

I will also install Mux which will help us with routing.

Let's look at some basic Go code, from here:

I've initialized a simple api using Mux

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.