-
Notifications
You must be signed in to change notification settings - Fork 82
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
RFC: Portal DB #285
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is wrong
Right now, all of the data that is part of portal tends to be sourced from other places. It would be really convenient/nice to have a piece of infrastructure that gave us the equivalent of a portal archive node, which was able to house all of the data that belongs in the portal network in the format that we use and in the access patterns that we need.
How can this be fixed?
My proposal is that we build a web application that acts as a data warehouse. Data would be accessed by either
content-key
orcontent-id
, probably via a HTTP/REST API.History network is going to be the simplest starting point. The application should probably have a relational model of all of the blocks by both number and hash (similar to how Glados holds this data) and then that should be tied relationaly to the associated content-key and content-id entries, with the actual data payloads being stored as binary blobs.
The application should have some simple tooling for populating the database from a reliable data source (like era1 files).
The text was updated successfully, but these errors were encountered: