Skip to content

Investigate whether our gem should store state on disk #4

@ethan-readyset

Description

@ethan-readyset

As of right now, this is more of a spike. We need to investigate 1) whether our gem needs to store state on disk and 2) what state our gem needs to store. This will depend on whether we want to provide a way for users to change routing decisions for queries at runtime.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions