|
|
# Table of Contents
|
|
|
|
|
|
# Platform Overview
|
|
|
# Core Platform Services and Components
|
|
|
|
|
|
# Core Services
|
|
|
|
|
|
The OSDU platform is a set of services and workflows orchestrated by an underlying cloud platform and deployed into your cloud environment of choice by infrastructure templates and deployment strategies provided by the CSP.
|
|
|
The OSDU platform is a set of services and workflows orchestrated by an underlying cloud platform and deployed into your cloud environment of choice by infrastructure templates and deployment strategies provided by the CSP (Cloud Service Provider).
|
|
|
|
|
|
The platform exposes a common set of APIs with a standard access pattern, security and other entitlement behavior that is recognized and replicated across the platform. These services are specialized for certain interactions and designed to scale independently.
|
|
|
|
... | ... | @@ -12,26 +10,44 @@ The core services can be orchestrated by the underlying platform and support CRU |
|
|
|
|
|
Indexing is done by the indexing service at the time of write, and indexes into an Elastic search instance setup by the CSP infrastructure. Elastic Search is the chosen indexing and search platform across all cloud providers because of its ability to index on coordinates and support polygon querying among other features.
|
|
|
|
|
|
The system supports history, lineage, and versioning of the data.
|
|
|
|
|
|
The system supports eventual consistency.
|
|
|
|
|
|
![image](uploads/e8fb65fee31fc116aea7af876bb6a346/image.png)
|
|
|
_Core services and data functional decomposition_
|
|
|
|
|
|
|
|
|
The system supports history, and versioning of the data. <more on this, and discuss extensibility and lineage>
|
|
|
|
|
|
The system supports eventual consistency. <show examples>
|
|
|
|
|
|
|
|
|
## Platform Architecture Overview
|
|
|
|
|
|
|
|
|
|
|
|
## Microservices
|
|
|
|
|
|
The base platform is composed of a set of microservices illustrated in the diagram. These microservices are accessed through a standard API architecture published using Open API standards. User and/or service identity is used to authenticate the users accessing the APIs.
|
|
|
|
|
|
|
|
|
For more information, a detailed inventory of the platform's core services and their APIs and documentation can be found on the following page : [Core Microservices](https://community.opengroup.org/osdu/documentation/-/wikis/Core-Services-Overview)
|
|
|
|
|
|
## Application Components and Technology Stack
|
|
|
|
|
|
## Microservices Documentation
|
|
|
### Core Dependencies
|
|
|
|
|
|
The following page has detailed documentation on each microservice: [Core Microservices](https://community.opengroup.org/osdu/documentation/-/wikis/Core-Services-Overview)
|
|
|
### Security, Entitlement and Compliance
|
|
|
|
|
|
## Platform Architecture (cross-CSP)
|
|
|
### Test Data
|
|
|
|
|
|
## Java Services Runtime
|
|
|
### Platform Validation
|
|
|
|
|
|
## Provider SPI
|
|
|
### Standard Logging Facade
|
|
|
|
|
|
##
|
|
|
### Provider SPI Standards
|
|
|
|
|
|
### Data Partitioning
|
|
|
|
|
|
### Language Standards
|
|
|
|
|
|
|
|
|
## Data Definition and Standards Documentation
|
... | ... | |