go-redsync/redsync

Distributed mutual exclusion lock using Redis for Go

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 15 minutes ago
Added to GitGenius on September 17th, 2026
Created on February 2nd, 2016
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 349
Total Stargazers: 4,048 (+0)
Total Subscribers: 23 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 29.5 hours
Mean response time: 130.3 days
90th percentile: 63.5 days
Tracked items: 11

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A 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

  • wontfix (11)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Redsync is a distributed mutual exclusion lock implementation using Redis for Go applications.

The tool solves the problem of coordinating access to shared resources across multiple processes or machines. It implements Redis-based locking by leveraging Redis commands to create locks that can be acquired and released by different instances of an application. The approach uses Redis as a central authority to manage lock state, allowing distributed systems to safely serialize access to critical sections without requiring a separate consensus system.

Developers should choose this tool when building Go applications that need distributed locking across multiple servers or processes and already have Redis infrastructure in place. It suits scenarios where lightweight coordination is needed without the overhead of dedicated consensus systems. The project is appropriate for teams comfortable managing Redis as a dependency and who need straightforward mutual exclusion semantics rather than more complex distributed coordination patterns.

The project maintains active engagement with its codebase, regularly addressing issues and accepting contributions that improve the implementation. Development shows responsiveness to bug reports and feature requests from users. The maintainers demonstrate commitment to keeping the tool compatible with current Go practices and Redis capabilities through ongoing updates and refinements.