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

How to represent a read-only Key-Value store? #43

Open
mpwarres opened this issue May 2, 2024 · 2 comments
Open

How to represent a read-only Key-Value store? #43

mpwarres opened this issue May 2, 2024 · 2 comments

Comments

@mpwarres
Copy link

mpwarres commented May 2, 2024

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?

@Mossaka
Copy link
Collaborator

Mossaka commented May 5, 2024

What will be the use cases for read-only key-value stores? Will wasi:runtime-config solve these use cases, which is a simply interface that provides read-only operations.

@thomastaylor312
Copy link
Collaborator

Yeah I'm definitely curious on the use case here. With the current interface, since it returns errors, you could create an implementation that returns an error on write ops. But I also understand you may want to have the interface indicate the difference

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants