resty VS go-retryablehttp

Check out the go-resty docs for more features

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

We have faced several network issue on our backend application written in golang with resty for inter service calls. We have seen large amount of network errors like `EOF, unexpected EOF, http: stream closed` because of which our APIs fail. Have you faced similar issue and what were the solutions you've implemented.

Go-resty makes it a lot easier to create a http client and much more readable for developers.

I don't use the simple http whenever i need to call any API from code . I just use resty its fairly easy to use and logging requests with it is quite easy

What are the advantages over https://github.com/go-resty/resty ? resty has `.R()` request builder.

We need to call PrinterService from the InvoiceGenerator. Therefore, we need an HTTP client in our project. Install Go’s resty HTTP client library with the following command.

Check out https://github.com/go-resty/resty

Both cases can be mitigated with automated retries. We went with hashicorp/go-retryablehttp as Echoes is built in Go. The library's default retry policy rightly doesn't consider a 401 response as a recoverable error, but this can be changed using the [CheckRetry hook](https://pkg.go.dev/github.com/hashicorp/go-retryablehttp#CheckRetry).