Difference between revisions of "Fusion Registry Overview"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
The Fusion Registry Core is responsible for all data collection, integration processing and storage. Its optimised query execution engine and SDMX data and metadata REST API make it suitable for external dissemination, and as a data source for internal analysis purposes. | The Fusion Registry Core is responsible for all data collection, integration processing and storage. Its optimised query execution engine and SDMX data and metadata REST API make it suitable for external dissemination, and as a data source for internal analysis purposes. | ||
− | + | The Fusion Registry Core is a monolithic Java web application which in the Enterprise Edition can be deployed in load-balanced clusters for scalability and resilience. | |
==Functionality== | ==Functionality== |
Revision as of 23:49, 20 February 2020
The main statistical data engine with an integrated SDMX Metadata Registry.
The Fusion Registry Core is responsible for all data collection, integration processing and storage. Its optimised query execution engine and SDMX data and metadata REST API make it suitable for external dissemination, and as a data source for internal analysis purposes.
The Fusion Registry Core is a monolithic Java web application which in the Enterprise Edition can be deployed in load-balanced clusters for scalability and resilience.
Functionality
Community | Data Essentials | Enterprise | Cloud | |
---|---|---|---|---|
Data Collection | Yes | Yes | Yes | Yes |
Data Integration | No | No | Yes | Yes |
Data Storage | No | No | Yes | Yes |
Data Structural Validation | Yes | Yes | Yes | Yes |
Data Transformation | Partial | Partial | Full | Full |
Data Conversion | Partial | Partial | Full | Full |
Data Dissemination | No | No | Yes | Yes |
Reference Metadata | No | No | Yes | Yes |
Audit | No | No | Yes | Yes |
Content Security | No | No | Yes | Yes |
SDMX REST API | No | No | Yes | No |
Extended REST API | No | Yes | Yes | Yes |