Guide for creating a distributed lock
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
Something similar to what @nviennot is doing on NoBrainer to guarantee uniqueness(using a dedicated table to manage the locks) would be nice for people who need this kind of stuff
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no target file, test, or documentation entry point. Review the documentation structure and the referenced NoBrainer approach first; done means adding a guide that explains creating a distributed lock with a dedicated table for uniqueness.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100