You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 3, 2023. It is now read-only.
DataHelix and DataHub have distinct benefits and advantages to engineering teams, whether it's the quick creation of systems data through config files or through the complex analysis of existing systems and data.
To understand the synthetic data landscape in FINOS, it's important to understand the synergies and differences between DataHub and DataHelix to stop confusion and provide clarity in this area.
This issue is to create a features and benefits matrix for DataHelix and DataHub to help the project teams define their roadmaps and to provide guidance to users exploring the synthetic data space.
Acceptance Criteria
Create a markdown file in DataHub or DataHelix where both projects can collaborate
Each team lists the problems their own project currently solves in a table similar to below
cc @andrewcarrblue and @grovesy
Description
DataHelix and DataHub have distinct benefits and advantages to engineering teams, whether it's the quick creation of systems data through config files or through the complex analysis of existing systems and data.
To understand the synthetic data landscape in FINOS, it's important to understand the synergies and differences between DataHub and DataHelix to stop confusion and provide clarity in this area.
This issue is to create a features and benefits matrix for DataHelix and DataHub to help the project teams define their roadmaps and to provide guidance to users exploring the synthetic data space.
Acceptance Criteria
TRUE
orFALSE
whether the own project delivers against listed feature benefitsThe text was updated successfully, but these errors were encountered: