home.social

#distributedlocking — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #distributedlocking, aggregated by home.social.

  1. If a lock holder crashes, the lock must expire via time-to-live. If the TTL is too short, a slow process may lose its lock while still executing, allowing a second process to proceed — a correctness failure in fintech.

    #DistributedLocking #FaultTolerance #Fintech

  2. If a lock holder crashes, the lock must expire via time-to-live. If the TTL is too short, a slow process may lose its lock while still executing, allowing a second process to proceed — a correctness failure in fintech.

    #DistributedLocking #FaultTolerance #Fintech

  3. Redis and ZooKeeper are widely used for distributed locking. Redis uses key expiry with a time-to-live. ZooKeeper uses ephemeral sequential nodes, where the client holding the lowest sequence number owns the lock.

    #DistributedLocking #Redis #ZooKeeper

  4. Redis and ZooKeeper are widely used for distributed locking. Redis uses key expiry with a time-to-live. ZooKeeper uses ephemeral sequential nodes, where the client holding the lowest sequence number owns the lock.

    #DistributedLocking #Redis #ZooKeeper

  5. A distributed lock ensures only one node among many executes an operation at a time. It enforces mutual exclusion across a distributed system to prevent race conditions on shared resources like account balances.

    #DistributedLocking #Fintech #DistributedSystems

  6. A distributed lock ensures only one node among many executes an operation at a time. It enforces mutual exclusion across a distributed system to prevent race conditions on shared resources like account balances.

    #DistributedLocking #Fintech #DistributedSystems