WebAssembly / WebAssembly/wasi-keyvalue
Atomic increment conflicts
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 54
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
For databases where an increment uses optimistic concurrency under the covers, increments could fail due to conflicts in the same way as swap. With the current design I think explicitly signalling a conflict would require a new e.g. increment-error type, though if a bigger redesign is imminent this could be considered then.
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the existing increment and swap operation definitions and their optimistic-concurrency behavior. Determine how conflicts are currently represented, whether increment needs a distinct error type, and whether a broader redesign is already appropriate; done means the API behavior and conflict signaling are specified consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- backend-api-design, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100