cenkalti/backoff

⏱ The exponential backoff algorithm in Go

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 38 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 17th, 2026
Created on February 26th, 2014
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 227
Total Stargazers: 4,078 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.1 hours
Mean response time: 75.8 days
90th percentile: 222.5 days
Tracked items: 39

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 8 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (11)
  • v5 (5)
  • feature request (3)
  • bug (2)
  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

backoff is a Go library that implements the exponential backoff algorithm.

The library solves the problem of handling transient failures in distributed systems by providing a way to retry failed operations with exponentially increasing delays between attempts. Rather than immediately retrying a failed operation or using fixed intervals, exponential backoff spreads out retry attempts over time, reducing load on the system and increasing the likelihood of success when dealing with temporary outages or resource contention. The library handles the calculation and management of these delay intervals automatically.

Developers should choose this library when building Go applications that need robust retry logic for network requests, database operations, or other potentially transient failures. It suits any project where you want to avoid overwhelming a struggling service with immediate repeated requests. The library is particularly valuable in microservices architectures, API clients, and distributed systems where graceful degradation during temporary failures is important.

The project maintains a focused, stable implementation with minimal churn in its codebase. Development activity shows consistent but measured engagement with the repository, suggesting a mature tool that does not require frequent updates to remain functional.