Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A storage backed distributed lock would ensure atomic operations support #116

Open
nmondal opened this issue Aug 4, 2024 · 1 comment
Open
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@nmondal
Copy link
Owner

nmondal commented Aug 4, 2024

We can practically have any usage, sans the locking. W/O Locking it is impossible to protect any resource. This resource can be anything that gets shared between two processors running on two separate machines.

Say we want to do seat booking with Cowj. It is all good - all w/o any database till we reach the problem of finite amount of seats. That pose a problem.

One solution could be creating a Storage key backed lock. The details needs to be thrashed out and proven.
But the problem exists. Solution is very trivial w/o the storage - just integrate with a Transactional Distributed System.
It is only if we want to avoid those, we get into this problem.

@nmondal nmondal added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Aug 4, 2024
@nmondal
Copy link
Owner Author

nmondal commented Aug 6, 2024

A very good start is from the iconic guy himself:
https://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant