shclisem
Simple HTTP Client Semaphore (by madman22)
backoff
⏱ The exponential backoff algorithm in Go (by cenkalti)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
shclisem
Posts with mentions or reviews of shclisem.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-10.
-
Queuing up API requests with waitgroups?
A Semaphore might be your best best, check out the code in my repo, https://github.com/madman22/shclisem
-
handling http response
here is my example that uses a drop in replace to use a semaphore to limit the number of in flight requests: https://github.com/madman22/shclisem
-
Reconnect to a server
As long as the pub/sub is an interface, you can create your own implementation that has reconnection and backoffs. I made my own http client that is a drop in replacement for the standard library http client with added methods for more features. https://github.com/madman22/shclisem as an example
backoff
Posts with mentions or reviews of backoff.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-07.
-
Retry operations with constant, delays and exponential backoff strategies
Why this instead of https://github.com/avast/retry-go or https://github.com/cenkalti/backoff ?
-
Gosyphus: Retries with exponential backoff
What about https://github.com/cenkalti/backoff?
-
Libraries you use most of your projects?
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
-
retry package for golang
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).
- How to implement a retry mechanism for goroutines?
-
Queuing up API requests with waitgroups?
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.