The latest articles on DEV Community by Kohki Chau (@autofun). https://dev.to/autofun https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1261027%2Ff1130f33-1cd9-4244-ad79-a0998e4b79b1.jpg https://dev.to/autofun en Kohki Chau Fri, 19 Jan 2024 15:17:20 +0000 https://dev.to/autofun/redis-distributed-lock-tips-5bca https://dev.to/autofun/redis-distributed-lock-tips-5bca <ol> <li>The algorithm requires a minimum of <strong>three Redis instances</strong> to work.</li> <li>The client generates a random value called <code>nonce</code> and tries to acquire a lock on a resource by sending a <code>SET</code> command to each of the Redis instances with the same <code>resource_name</code> and <code>nonce</code> values.</li> <li>The <code>SET</code> command should include an <code>EX</code> parameter to set an expiration time for the lock.</li> <li>If the client can acquire the lock on a majority of the Redis instances, it is considered to have acquired the lock.</li> <li>If the client fails to acquire the lock on a majority of the Redis instances, it should release the lock on all the instances where it was acquired.</li> <li>To release the lock, the client sends a <code>DEL</code> command to all the Redis instances where it had acquired the lock.</li> </ol> <p><a href="https://redis.io/docs/manual/patterns/distributed-locks/">The Redlock algorithm is designed to provide <strong>mutual exclusion</strong>, <strong>deadlock-free</strong> and <strong>fault-tolerant</strong> guarantees </a></p> redis distributedlock