spin
spin copied to clipboard
Implement a key/value store interface
Spin applications should have a default key/value store implementation available at runtime, ideally following https://github.com/fermyon/wasi-experimental-toolkit.
Some things to nail down:
- Is this envisaged as being persistent a la object storage, or transient a la cache?
- What is the scope of a store - that is, if a handler requests a store from the runtime, should it get a private one (seems unlikely), one shared with other instances of the component, or with other instances of the app, or with other apps on the node?
@radu-matei is this still of interest given that we now support redis? Are we hoping to also support a local KV store? Should we narrow the scope of this issue?