These are the architecturally significant use cases for the data ecosystem
Minimum Viable Architecture
OSDU R1 is the minimum footprint to highlight alignment and conflicts between OSDU and OpenDES. We recognize that R1 is a fraction of OSDU goals, but it should provide the basis for converging the two architectures as the basis for R2 which will focus on evolution.
The primary goal of OSDU R2 is to achieve a single baseline based on a converged architecture/implementation running on multiple platforms that extends the R1 release by adding support for Seismic files.
This is the minimum workflow footprint to assess the cost of porting OpenDES to run on multiple clouds. This will exercise the Core services that are architecturally significant.
These are the open source tools/libraries that will be used across all implementations of OSDU.
Minimum Viable Product
This is one of the older and broader MVP documents that was used to define the basic functionality of the data ecosystem. Since then the stories have been maintained a much finer granularity within Azure DevOps.
- Single customer, multi-region
- Single deployment, multi-customer (aka multi-tenant)
- Multi-region, multi-customer
OSDU Developer Stories
- OSDU Developer Environments
- Implementing Commercial Extensions to the OSDU Data Platform
- Marketplaces for OSDU Software
- Developing a Domain Data Management System (DDMS)