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
Last revisionBoth sides next revision
distributed_computing:locks [2017/09/09 14:00] – [Implementations] phreazerdistributed_computing:locks [2017/09/09 14:17] – [Implementations] phreazer
Line 13: Line 13:
   * 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
 +  * Google Chubby
 +  * Distributed locks with Redis: https://redis.io/topics/distlock
   * Relational database   * Relational database
     * Linearizable writes     * 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.       * 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.txt
  • Last modified: 2017/09/09 14:30
  • by phreazer