Skip to content

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

@mpwarres

Description

@mpwarres

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions