Redis backends
Latest stable Based on Leader release 0.4.0
Choose Lettuce for command-level control or Redisson for its client ecosystem while respecting thread-bound ownership.
Common contract
Section titled “Common contract”Both modules provide single, group, suspend, factory, state, and strategic variants. They use owner tokens for conditional release and the shared lease auto-extender. Redis server availability and key expiry are part of the correctness boundary.
Lettuce
Section titled “Lettuce”Lettuce exposes sync and coroutine-friendly command paths and is a good fit when the application already owns a Lettuce connection. Validate connection lifecycle and command timeout separately from election waitTime.
Redisson
Section titled “Redisson”Redisson integrates with RLock/semaphore-style facilities. Some ownership is tied to the acquiring thread; extending from another thread yields WrongThread. The 0.4.0 elector passes an explicit lease, so benchmarked autoExtend refers to bluetape4k’s shared extender, not Redisson’s native watchdog mode.
Release sources
Section titled “Release sources”leader-redis-lettuce/README.mdleader-redis-redisson/README.mddocs/benchmarks/2026-06-01-issue-422-redis-lease-extension-throughput.json