backoff VS examples

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

What about https://github.com/cenkalti/backoff?

In addition to the ones you mentioned, I also always use: + sqlc - Compile SQL to type-safe code + gqlgen - generate GraphQL server from schema + oapi-codegen - Go client and server boilerplate from OpenAPI 3 specifications + pester - Go http calls with retries and backoff + backoff - exponential backoff algorithm in Go

May I suggest directions to improve? - add option for exponential or linear backoff - stop early on non-retriable errors Example: https://pkg.go.dev/github.com/cenkalti/backoff/v4 (do not know about its author, just a package I've been using).

I have used https://github.com/cenkalti/backoff a few years ago and I don't know if it's the best candidate at this point but it's worth to consider in combination with or as an alternative to x/time/rate if you are going that route.

The book "Cloud Native Go" does it like this: https://github.com/cloud-native-go/examples/blob/b7a623e9a45d8ca71979eee220d43503588565fb/ch04/retry.go

The book Cloud Native Go https://www.oreilly.com/library/view/cloud-native-go/9781492076322/ also has an implementation in it. Here you can find the code https://github.com/cloud-native-go/examples/tree/main/ch04

I haven’t read the book you mentioned, but I did just get Cloud Native Go and am loving it so far. It sounds like Cloud Native Go might be what you’re after because it includes actual patterns for handling things like retries and backoff, but also goes into using tools like Docker and gRPC and how to architect your services. I’m only on chapter 4 so far, but I’ve already learned a bunch of practical things that I feel good about recommending it already.