WebAssembly / WebAssembly/wasi-keyvalue
How to represent a read-only Key-Value store?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 54
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
What would the recommended way to represent a read-only key-value store (populated from or fronting some other source) with these interfaces--have it export store but return errors from bucket.set and .delete calls? Is it worth considering having a read-only store interface, or is this use case too niche to warrant a separate interface?
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 reviewing the existing store and bucket interfaces referenced in the issue. Determine how a read-only key-value store should expose reads and reject set/delete operations, then establish whether a separate read-only store interface is warranted. Done means the representation and interface decision are documented or agreed upon.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100