This lock mechanism works only for one process (worker).
live-mutex: has horrible API and doesn't allow to check if an key is currently locked.
proper-filelock: No way to do a correct mutex locking with event-driven blocking acquire() method.
redislock: Very bad performance on high-load (when multiple locks on the same key wait, since it loops)
mongodb lock: even worse performance than redis. Jesus.
This lock mechanism works only for one process (worker).
live-mutex: has horrible API and doesn't allow to check if an key is currently locked. proper-filelock: No way to do a correct mutex locking with event-driven blocking acquire() method. redislock: Very bad performance on high-load (when multiple locks on the same key
wait
, since it loops) mongodb lock: even worse performance than redis. Jesus.