Explore projects

Library for Time-series Store SPI implementations

The Time-series Service provides functionality for fetching stored time-series by entity, property, source and date-time span. The time-series are handled in a bi-temporal approach, where the version time is the time where the fact has been stored and the physical time where the transaction has happened.

The Property Discovery Service features enables the user to query and scan through the catalog of the available set of properties using various search criteria.

The Time-series Storage Core (or internal) Service is a final step in time-series ingestion pipeline. Processes published ingestion messages and stores data to the Time-series Storage.

Time-series Query Core (or internal) Service provides low level APIs for fetching data streams from Time-series Store.

The Structure Storage Core (or internal) Service enables entities and their relationships management.

The Domain Model Core (or internal) Service is a catalog representing the production domain. It has the information about supported entity types, associated properties with these entity types. A property contains information that describes the characteristics of a time-series, such as the unique property identifier (descriptor), data type, measurement, etc.

The Structure Query Core (or internal) Service provides low level APIs for fetching entities and their relationships from Hierarchy Store.

Library for common Redis functionality

Library for common Scala functionality

The Time-series Management Service allows users to ingest time-series bulk data as a array of data points. The data can be written for set of entities, properties and source. User access is restricted through entitlements. The data ingested supports bi-temporality.

Library for core (or internal) API definitions (gRPC stubs)

The Entity Management Service provides a set of APIs that enables the user to register OSDU Storage records as entities in Production DDMS, put them into relationships (hierarchies) and discover existing entities based on search criteria. Entities are defined through a type like well, meter, valve or platform. Two entities can have multiple entity relationships of a different types. The entities can be retrieved from the system in graph format with upward or downward graph traversal.

Library for shared components like httpclient, logging, units of measurement handling, etc.

The Time-series Publisher Core (or internal) Service is a part of time-series ingestion pipeline. Processes ingestion messaging queue and prepares data for Time-series Storage Core Service.

The Cache Job is an internal background cron job that caches available entity hierarchies and time-series stream mapping for further rapid access by other services.

Library for common security functionality

Library for Pekko http and streams common functionality

Library for Messaging Queue SPI implementations

Library for integration with OSDU Core services