retry-go VS Echo

Why this instead of https://github.com/avast/retry-go or https://github.com/cenkalti/backoff ?

What is that advantage of your package compared to other ones like https://github.com/avast/retry-go?

processCreateEmail handling create email events, it's start tracing span, increase metrics counters, then unmarshal message data, and call usecase create method, if it fails, we retry for 3 times using retry-go, if it still fails, we check is the current message redelivered and if redelivery count > maxRedeliveryCount(it's up to your business logic, here is 3 times limit), handling error cases can be very different and depends on your service business logic, in this example used Dead Letter Queue approach.

Workers validate message body then call usecase, if it's returns error, try for retry, good library for retry is retry-go, if again fails, publish error message to very simple Dead Letter Queue as i said, didn't implement here any interesting business logic, so in real production we have to handle error cases in the better way. And after message success processed commit it.

echo vs. fasthttp Selection: If the echo framework has been decided to be used, it is not recommended to consider fasthttp anymore. Although echo supported fasthttp in version 2, the author of echo explained the reasons for giving up in https://github.com/labstack/echo/issues/665, mainly to maintain the simplicity of the framework and community compatibility, and to use the standard library as much as possible. This enables echo to better integrate with the community ecosystem while maintaining high performance.

Uber Fx is a dependency injection framework for golang build by Uber which is integrated in all the golang services in Uber to have uniform structure of code across services, code reuse is easier and makes servers efficient. Echo is one of the most popular go webserver framework known for being high performant, extensible and minimalist.

Echo: Known for great docs and HTTP/2 support.

I am over Gin and have been for years yet everyone keeps using it because it has inertia. The docs are garbage.

Big fan of Echo and it has much better docs.

https://echo.labstack.com/

I was initially using Go Fiber, because that is what the example app I was piggybacking off of used. It however does not compile when building for the browser. I tested out Gin and Echo. They both compiled and since my current project at work uses Echo I chose to use that here.

This post is all about Golang so that's the back-end language. However we are going to use the Echo Framework and GORM to speedup development.

Echo GitHub Repository

Echo for the web server.

Echo - web framework for Go

The three behaviors I've described that we want all depend on two things, the first of which is "idiomatic error handling". We need to be able to simply return err in our handlers. Unfortunately, the standard libray doesn't give us this. But some third-party frameworks do. The most popular one I'm familiar with is labstack echo, whose HandlerFunc looks like this: