From cbcd06af0e4896e2ec77833ebc7ee84faee5925e Mon Sep 17 00:00:00 2001 From: Rustam Ibragimov <iamdaiver@gmail.com> Date: Wed, 10 Apr 2024 09:50:47 +0300 Subject: [PATCH] [doc/distributed_locks] new ruby implementation --- content/develop/use/patterns/distributed-locks.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/develop/use/patterns/distributed-locks.md b/content/develop/use/patterns/distributed-locks.md index 2bbccf4464..ba3a1e515b 100644 --- a/content/develop/use/patterns/distributed-locks.md +++ b/content/develop/use/patterns/distributed-locks.md @@ -38,6 +38,7 @@ Before describing the algorithm, here are a few links to implementations already available that can be used for reference. * [Redlock-rb](https://github.com/antirez/redlock-rb) (Ruby implementation). There is also a [fork of Redlock-rb](https://github.com/leandromoreira/redlock-rb) that adds a gem for easy distribution. +* [RedisQueuedLocks](https://github.com/0exp/redis_queued_locks) (Ruby implementation). * [Redlock-py](https://github.com/SPSCommerce/redlock-py) (Python implementation). * [Pottery](https://github.com/brainix/pottery#redlock) (Python implementation). * [Aioredlock](https://github.com/joanvila/aioredlock) (Asyncio Python implementation).