generated from application-research/next-sass
-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Planning] Delta-DM V2 Planning & Discovery #76
Comments
Edge URID will be the first major INPUTS component application-research/delta-edge#51 |
Closing as this issue is in the wrong repo - continued: application-research/delta-dm#83 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today, Delta-DM is modelled around the concept of datasets that are imported once and then don't change very much. It's good for static, archival use case, but is not very flexible when it comes to continuously growing datasets and dynamic data sources/participants.
Conceptually, the next iteration of Delta DM will continuous data streams / inputs, and a feedback loop to manage the dealmaking for that content.
Simply put, In DDM V2 we will model things around INPUTS and OUTPUTS
Both Inputs and Outputs will be modular and allow different components to be attached as necessary for the client's use case / strategy.
The core functionality of DDM is a tracking database to facilitate replicating that data out to the Filecoin network in a variety of ways.
INPUTS
OUTPUTS
The text was updated successfully, but these errors were encountered: