Difference between revisions of "Fusion Edge Server"
Jump to navigation
Jump to search
(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...") |
|||
| Line 4: | Line 4: | ||
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. | 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. | ||
| + | |||
| + | No database is required.<br> | ||
| + | Once primed with data, Fusion Edge Servers are completely autonomous requiring no connection back through the firewall to services on the private network. | ||
==Key Use Cases== | ==Key Use Cases== | ||
| − | * | + | * Driving public dissemination services |
==Specification== | ==Specification== | ||
| Line 15: | Line 18: | ||
| Apllication Type || Server | | Apllication Type || Server | ||
|- | |- | ||
| − | | User Interface || | + | | User Interface || No user interface |
|- | |- | ||
| − | | API || SDMX-compliant REST API with proprietary extensions [https://demo.metadatatechnology.com/FusionRegistry/webservice/data.html Data API Example] | + | | API || SDMX-compliant REST API with proprietary extensions, compatible with that provided by the Fusion Registry Core [https://demo.metadatatechnology.com/FusionRegistry/webservice/data.html Data API Example] |
|- | |- | ||
| Technology || Java web application | | Technology || Java web application | ||
| Line 23: | Line 26: | ||
| Compatible platforms || Linux, Windows, Mac and other platforms supporting a Java web runtime environment | | 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 | + | | Minimum operating configuration || The minimim list of components required to deploy a Fusion Edge Server are:<br> |
The Fusion Registry web app (WAR file)<br> | The Fusion Registry web app (WAR file)<br> | ||
Java Runtime Environment<br> | Java Runtime Environment<br> | ||
| − | Java web application server (for instance Apache Tomcat) | + | Java web application server (for instance Apache Tomcat) |
| − | |||
|} | |} | ||
[[Category:Components and Modules]] | [[Category:Components and Modules]] | ||
| − | ==Functionality | + | ==Functionality== |
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| − | ! style="width:300px"| !! style="width:150px" | | + | ! style="width:300px"| !! style="width:150px" | Fusion Edge Server |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| − | | | + | | SDMX REST API || Read only SDMX-compliant API for structures and data |
| + | | | ||
|} | |} | ||
Revision as of 08:10, 14 September 2020
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.
No database is required.
Once primed with data, Fusion Edge Servers are completely autonomous requiring no connection back through the firewall to services on the private network.
Key Use Cases
- Driving public dissemination services
Specification
| Header text | Header text |
|---|---|
| Apllication Type | Server |
| User Interface | No user interface |
| API | SDMX-compliant REST API with proprietary extensions, compatible with that provided by the Fusion Registry Core 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 Edge Server are: The Fusion Registry web app (WAR file) |
Functionality
| Fusion Edge Server | ||
|---|---|---|
| SDMX REST API | Read only SDMX-compliant API for structures and data |
