Show HN: Lockable – sync locks for distributed systems

Re:Show HN: Lockable – sync locks for distributed systems by keyless_ on Saturday June 18, 2022 @08:12AM (#31789154)

Unfortunately, it doesn't. That was actually the reason I built this originally - there's no easy way to control read/write access to a file on S3 without using some sort of external locking system.

[ Parent | on HN ]

Re:Show HN: Lockable – sync locks for distributed systems by IanCal on Saturday June 18, 2022 @09:12AM (#31789527)

You can add locks to objects, which restricts who can delete them and how, but requires bucket wide settings.

[ Parent | on HN ]

Re:Show HN: Lockable – sync locks for distributed systems by maest on Saturday June 18, 2022 @12:42PM (#31791474)

BTW, this is true, but that is not locking in the "sync locking" sense.

[ Parent | on HN ]

Re:Show HN: Lockable – sync locks for distributed systems by IanCal on Saturday June 18, 2022 @05:30PM (#31794005)

It's not the intended purpose but they can be used like this. Lock files can be written, will fail if they already exist - that gets you a distributed equivalent to flock doesn't it?

[ Parent | on HN ]

Re:Show HN: Lockable – sync locks for distributed systems by GordonS on Saturday June 18, 2022 @10:09AM (#31789975)

Have you looked at Azure Blob Storage's lock feature? Could that be used?

[ Parent | on HN ]

Re:Show HN: Lockable – sync locks for distributed systems by killingtime74 on Saturday June 18, 2022 @08:16AM (#31789170)

Did Zookeeper or Etcd not suit your needs?

[ Parent | on HN ]

Re:Show HN: Lockable – sync locks for distributed systems by keyless_ on Saturday June 18, 2022 @08:56AM (#31789419)

They are valid solutions for this use-case; the main drawback is you need to set up and maintain a ZooKeeper cluster. Lockable is intended as a simpler and faster-to-use alternative.

[ Parent | on HN ]