cenkalti/backoff
⏱ The exponential backoff algorithm in Go observed · 2026-08-28
Health v2 · maintenance only
73/100
- Activity 90
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4572
- days_rel: n/a
- days_push: 64
- n_releases_24m: 0
Adoption not part of the score
4054 stars · 221 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
A Go library implementing the exponential backoff algorithm with a Retry helper for retrying operations. It supports configurable retry limits, permanent errors, and context-based timeouts.
Use cases
- retry failed http requests with exponential backoff
- add retry logic to flaky network calls in go
- rate-limit retries when calling an unstable api
- retry database or service operations until success
- stop retrying on permanent client errors
When to choose
- you need battle-tested exponential backoff in a Go project
- you want fine-grained control over retry limits, timing, and error classification
- you need context-aware cancellation of retry loops
When to avoid
- you need retries in a language other than Go
- you want a full circuit-breaker or resilience framework rather than just backoff
- your retry policy requires distributed coordination across services
Facets
library · maturity stable
concurrency error-handling http-client developer-tools backend networking go cross-platform retry exponential-backoff resilience rate-limiting
1 source
- readme: https://github.com/cenkalti/backoff · fetched 2026-08-28 · 90dea3e7c783
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| cenkalti/backoff | main | 73 |
For agents
markdown · JSON · MCP: product_card(name="cenkalti/backoff")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem