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

feat: persistent storage for hub data #61

Closed
varunsrin opened this issue Aug 15, 2022 · 1 comment
Closed

feat: persistent storage for hub data #61

varunsrin opened this issue Aug 15, 2022 · 1 comment
Assignees
Milestone

Comments

@varunsrin
Copy link
Member

Hub data should be persisted to a reliable data store like Postgres, Redis or equivalent.

This is important for v2 because the Hub needs to be run as a service in the cloud that can be restarted. The correct long term design might be to use a low-level kv-store like rocksdb or levelsdb, but we're ok cutting corners a bit to ship quickly and then refactor it on later. It's important that we use a simple querying and table layout so that we can migrate later when necessary.

@varunsrin varunsrin added this to the v2.0.0 milestone Aug 15, 2022
@varunsrin varunsrin changed the title Persistent storage for hub data feat: persistent storage for hub data Sep 26, 2022
@pfletcherhill pfletcherhill self-assigned this Sep 26, 2022
@pfletcherhill
Copy link
Contributor

Rocksdb implemented with #107

This issue was closed.
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

2 participants