Fiber VS Echo

I'm mostly playing around with Fiber.

📌 Note: Examples of code for these microservices will be at Go language and the Fiber web framework, since that's my main stack (at the moment).

Check Fiber, here.

Actually I don't think there is a real standard one. But I do very like using https://gofiber.io/. It's built on top of fasthttp which is one of the fastest Http severs out there.

☝️ Note: I will give all the code samples in Go with Fiber web framework, since this is my main language & framework for backend development at the moment.

Furthermore, in the example below, I took code from my project written using the Fiber web framework. So, some elements from its libraries are present there. Don't be scared, the main thing here is to understand the principle of validation itself.

Go-fiber

NodeJs has enjoyed a lot of love from people building backend services for the past decade. Developing APIs the Express way is super developer friendly for both polished NodeJs developers and new Go Developers. Thus Fiber was built with Express in mind. Fiber is a web framework for Go with APIs readiness from scratch, middleware support and super fast performance. We will be making use of Fiber to create our web API.

The framework I'm going to use is fiber and the ZeroMQ client that I'm going to use is zmq4.

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.

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/