Fusion Edge Server

From Fusion Registry Wiki
Revision as of 08:01, 14 September 2020 by Glenn (talk | contribs) (Created page with "'''High-performance data dissemination server.''' A light-weight SDMX data and metadata REST API server designed to be deployed in clusters in the DMZ or at the network edge...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

High-performance data dissemination server.

A light-weight SDMX data and metadata REST API server designed to be deployed in clusters in the DMZ or at the network edge for scalable, fault-tolerant public data dissemination use cases.

A typical configuration consists of a private Fusion Registry Core installation and a cluster of between two and four Fusion Edge Servers that drive the actual dissemination services such as web data portals and public APIs. Data is published for dissemination by exporting a ZIP file from the Fusion Registry Core containing all of the data and structures. The ZIP file is pushed to each of the Fusion Edge Servers using any suitable means like FTP or WebDAV. On receipt, the Edge Servers load the new data and start serving it, either immediately or at a defined time.

Key Use Cases

  • Public dissemination services

Specification

Header text Header text
Apllication Type Server
User Interface Web user interface accessible using a standard web browser Live Demo
API SDMX-compliant REST API with proprietary extensions Data API Example
Technology Java web application
Compatible platforms Linux, Windows, Mac and other platforms supporting a Java web runtime environment
Minimum operating configuration The minimim list of components required to deploy a Fusion Registry Core service are:

The Fusion Registry web app (WAR file)
Java Runtime Environment
Java web application server (for instance Apache Tomcat)
SQL database (MySQL, SQL Server or Oracle

Functionality by Edition

Community Data Essentials Enterprise Cloud
Structural Metadata Registry Full Full Full Full
Data Collection No One data provider, pull from registered data sources not supported Full Full
Data Integration No Registry managed SQL data stores only Full Registry managed datastores and registered data sources only
Data Storage No Registry managed SQL data stores only Full Full
Data Structural Validation Full Full Full Full
Data Business Rules Validation using Metadata Technology's proprietary expression language Arithmetic rules only Arithmetric rules only Full Full
Data Structural Transformation Full Full Full Full
Time Series Calculations No No Full Full
Data Conversion SDMX formats only Full Full Full
Data Query Execution Engine No Full Full Full
Mapped Datasets No Full Full Full
Reference Metadata No No Full Full
Audit No No Full Full
Content Security No No Full Full
SDMX REST API Structures only Full Full Full
Extended REST API Validation and transformation only Full Full Full
VTL source code repository No - Planned for April 2021
VTL execution engine No - Planned for 2021/2022