I am researching the best software for distributed locking purposes, and came across this article: https://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html

I think the Redlock algorithm is a poor choice because it is “neither fish nor fowl”: it is unnecessarily heavyweight and expensive for efficiency-optimization locks, but it is not sufficiently safe for situations in which correctness depends on the lock.

I am looking for a database with guaranteed "correctness." I believe EOSIO has this feature, but I am wondering how it compares to current distributed locking mechanisms performance-wise. To be clear, I am referring to spinning up an independent instance of the EOSIO software, not an application on the public EOS chain. Thanks!

  • When you say performance-wise, what metrics are you specifically referring to? – Phillip Hamnett - EOS42 Jul 9 '19 at 21:43
  • Specifically, I am interested in maintaining low latency under high db transaction load. Memory is less important. – wass Jul 9 '19 at 23:44

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.