| Info |
|---|
From Since version 3.1.0 in the Control Panel-KickOff, Ontologies have been renamed referred to as "Entities" in the Control Panel. This does not alter any functionality, simply ; the nomenclature has simply been changed for a better understanding of the concept. |
The information that comes from the intake and processing is stored in the Semantic Data Hub of the platform, as we have said is the platform's persistence engine.
...
It supports the storage of information in different stores repositories (currently supported MongoDB, Relational Databases, Elasticsearch, Kudu, BigQuery, HIVE, CosmosDB and at query level any JDBC-driven DB) in addition to always allowing to query in SQL whatever the underlying repository.
...
Onesait Platform proposes a Data Centric Architecture
...
, i.e. an architecture where data is the main and permanent asset, while applications come and go. In these architectures the data model precedes the implementation of any given application and will be valid long after they are replaced.
...
In the platform it is supported through the concept of Entity (also called Ontology)
...
, this concept is
...
the one that allows to isolate the platform
...
from the underlying persistence technologies by
...
providing a SQL abstraction layer
...
. The information coming from the ingestion and processing is stored in the Semantic Data Hub of the platform, as we have said it is the persistence engine of the platform.
...
Its main features:
The Platform allows, depending on the requirements of each project (volumes of information in real and historical time, mostly read or write access, more analytical processes, previously existing technologies in customers, etc.) select the persistence engine more adequately, conceptually these concepts are handled on platform:
Real Time Database (RealTimeDB): It is designed to support a large volume of inserts and online queries very efficiently. The platform abstracts from the underlying technology allowing to use BD as Mongo, Elastic, Kudu, relational BD, ...
Historical and Analytical Database (HistoricalDB): It is designed to store all the information that is no longer part of the online world (for example, information from previous years that is no longer consulted) and to support analytical processes that extract knowledge of this data (algorithms). The platform supports technologies such as HIVE (with Impala or Presto for online consultations), SAP HANA, BigQuery, CosmosDB, SparkSQL, ...
Staging Area: It allows you to store raw and unprocessed files by the platform, for later intake. HDFS is usually used as storage although the platform allows others like GridFS to be used.
GIS Database: It allows the storage of geographic information and its subsequent consultation and processing, the platform supports MongoDB, Elastic, PostGIS among others.
All the definition and management of these entities is done from the Control Panel of the Platform:
List of Entities / Ontologies (seen by Administrator Role) with visibility levels, ...
...