bsm/redislock
Simplified distributed locking implementation using Redis observed · 2026-08-28
Health v2 · maintenance only
72/100
- Activity 89
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2627
- days_rel: n/a
- days_push: 67
- n_releases_24m: 0
Adoption not part of the score
1767 stars · 165 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A Go library providing a simplified distributed locking implementation built on Redis. It supports obtaining, refreshing, releasing, and TTL-checking locks, plus fencing tokens for safe lock-loss mitigation.
Use cases
- implement distributed locks across multiple service instances
- prevent concurrent cron jobs from running twice
- coordinate access to a shared resource using Redis
- add fencing tokens to distributed locking
- acquire and refresh locks with TTL in Go
- build a mutex backed by Redis
When to choose
- you need a small, focused distributed lock library for Go with Redis
- you want fencing token support to guard against GC-pause lock loss
- you already use go-redis and want a simple Obtain/Refresh/Release API
When to avoid
- you need multi-node consensus locking without trusting a single Redis instance (e.g. Redlock across clusters)
- your project is not in Go
- you need locks persisted outside Redis
Facets
library · maturity active
caching concurrency database-driver databases microservices developer-tools go windows self-hosted redis distributed-lock golang fencing-tokens mutex synchronization linux macos docker
1 source
- readme: https://github.com/bsm/redislock · fetched 2026-08-28 · 714b461338dd
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| bsm/redislock | main | 72 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem