distributed_computing:locks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
distributed_computing:locks [2017/09/09 13:46] – [Implementations] phreazerdistributed_computing:locks [2017/09/09 14:30] (current) phreazer
Line 11: Line 11:
 ====== Implementations ====== ====== Implementations ======
  
-Distributed locking with Zoo-Keeper: https://dzone.com/articles/distributed-lock-using +  * Distributed locking with Zoo-Keeper: https://dzone.com/articles/distributed-lock-using 
-Hashicorp Consul: https://www.consul.io/docs/guides/semaphore.html +  Hashicorp Consul: https://www.consul.io/docs/guides/semaphore.html 
-Relational database:+  * Google Chubby 
 +  * Distributed locks with Redis: https://redis.io/topics/distlock 
 +    * Not recommended when lock should be used for guarantee correctness (http://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html) 
 +  * Relational database 
 +    * Fencing tokens  
 +    * Linearizable writes 
 +      * Writes should appear to be instantaneous. Once a write completes, all later reads should return the value of that write or the value of a later write. Once a read returns a particular value, all later reads should return that value or the value of a later write.
  • distributed_computing/locks.1504957601.txt.gz
  • Last modified: 2017/09/09 13:46
  • by phreazer