EdgeServer - Revision history

Vmurrell at 15:30, 11 September 2023

2023-09-11T15:30:04Z

Vmurrell at 15:29, 11 September 2023

2023-09-11T15:29:43Z

Vmurrell at 13:40, 16 August 2023

2023-08-16T13:40:26Z

Mnelson: /* Design */

2022-08-30T09:39:54Z

‎Design

Mnelson: /* Performance and Durability */

2022-08-29T10:25:38Z

‎Performance and Durability

Mnelson: /* Performance and Durability */

2022-08-29T10:23:43Z

‎Performance and Durability

Mnelson: /* Overview */

2022-08-29T10:09:07Z

‎Overview

Mnelson: /* Overview */

2022-08-29T10:03:53Z

‎Overview

Mnelson: /* Overview */

2022-08-29T09:59:52Z

‎Overview

Mnelson: /* Overview */

2022-08-29T09:59:38Z

‎Overview

@@ Line 1: / Line 1: @@
 [[Category:Fusion Edge Server]]
-[[:Category:How_to_FES]]
+[[Category:How_to_FES]]
 == Overview ==
 The Fusion Edge Server is a Java web application, it’s responsibility is to host SDMX web services for the dissemination of data and related structural and reference metadata.  The web services support all [https://wiki.sdmxcloud.org/Category:SdmxDataFormat Data Formats] and Structure Formats supported by Fusion Registry as such Fusion Edge Server can be used as a direct replacement for the dissemination services provided by Fusion Registry.

@@ Line 1: / Line 1: @@
 [[Category:Fusion Edge Server]]
 == Overview ==
 The Fusion Edge Server is a Java web application, it’s responsibility is to host SDMX web services for the dissemination of data and related structural and reference metadata.  The web services support all [https://wiki.sdmxcloud.org/Category:SdmxDataFormat Data Formats] and Structure Formats supported by Fusion Registry as such Fusion Edge Server can be used as a direct replacement for the dissemination services provided by Fusion Registry.

← Older revision		Revision as of 13:40, 16 August 2023
Line 1:		Line 1:
		+	[[Category:Fusion Edge Server]]
	== Overview ==		== Overview ==
	The Fusion Edge Server is a Java web application, it’s responsibility is to host SDMX web services for the dissemination of data and related structural and reference metadata. The web services support all [https://wiki.sdmxcloud.org/Category:SdmxDataFormat Data Formats] and Structure Formats supported by Fusion Registry as such Fusion Edge Server can be used as a direct replacement for the dissemination services provided by Fusion Registry.		The Fusion Edge Server is a Java web application, it’s responsibility is to host SDMX web services for the dissemination of data and related structural and reference metadata. The web services support all [https://wiki.sdmxcloud.org/Category:SdmxDataFormat Data Formats] and Structure Formats supported by Fusion Registry as such Fusion Edge Server can be used as a direct replacement for the dissemination services provided by Fusion Registry.

@@ Line 18: / Line 18: @@
 == Design ==
-The Fusion Edge Server reads into memory a pre-compiled Environment. An Environment is built from a collection of SDMX structure and data files, and it is this information which is made available via the public web services of Fusion Edge Server.  The Fusion Edge Compiler is used to build the Environment, it does so by simply reading files on a file system and converting these into read only stores of information which can be rapidly ingested by Fusion Edge Server.  The input of the Fusion Edge Compiler is SDMX files, the output of a Fusion Edge Compiler are a collection of files which comprise the Environment.
+The Fusion Edge Server reads into memory a pre-compiled Environment. An [[Edge_Server_Environment|Environment]] is built from a collection of SDMX structure and data files, and it is this information which is made available via the public web services of Fusion Edge Server.  The Fusion Edge Compiler is used to build the [[Edge_Server_Environment|Environment]], it does so by simply reading files on a file system and converting these into read only stores of information which can be rapidly ingested by Fusion Edge Server.  The input of the Fusion Edge Compiler is SDMX files, the output of a Fusion Edge Compiler are a collection of files which comprise the [[Edge_Server_Environment|Environment]].
 Publishing new content to the Fusion Edge Server is simply a case of moving the Environment to a location that can be read by Fusion Edge Server.  Fusion Edge Server can be configured to automatically poll for updates (dynamic mode), or it can be configured to only read an Environment on application startup (static mode).

← Older revision		Revision as of 10:25, 29 August 2022
Line 36:		Line 36:

	=== Performance and Durability ===		=== Performance and Durability ===
		+	[[File:Edge Server Performance.png\|thumb\|Edge Server Performance]]
	The Fusion Edge Server is built to be highly performant, even under extreme load from multiple concurrent users. It uses a purpose built in-memory time series database, augmented with a custom caching layer, both of which have been tuned to work with the SDMX data and metadata model. The caching layer, for instance, knows when two data queries refer to the same data sub-cube even if the queries are expressed differently in the URL. Query optimisation similarly ensures that multiple concurrent queries for the same data are executed only once, directing the subsequent requests to the cached data once it has been built.		The Fusion Edge Server is built to be highly performant, even under extreme load from multiple concurrent users. It uses a purpose built in-memory time series database, augmented with a custom caching layer, both of which have been tuned to work with the SDMX data and metadata model. The caching layer, for instance, knows when two data queries refer to the same data sub-cube even if the queries are expressed differently in the URL. Query optimisation similarly ensures that multiple concurrent queries for the same data are executed only once, directing the subsequent requests to the cached data once it has been built.

@@ Line 38: / Line 38: @@
 The Fusion Edge Server is built to be highly performant, even under extreme load from multiple concurrent users.  It uses a purpose built in-memory time series database, augmented with a custom caching layer, both of which have been tuned to work with the SDMX data and metadata model.  The caching layer, for instance, knows when two data queries refer to the same data sub-cube even if the queries are expressed differently in the URL.  Query optimisation similarly ensures that multiple concurrent queries for the same data are executed only once, directing the subsequent requests to the cached data once it has been built.
-The Fusion Edge Server loads the pre-compiled content into memory on application startup, an Edge Server hosting 18 datasets, with 700k series and 50 milliion observations will startup and be ready to serve queries in as little as 20 seconds.  The content can be served from central shared location, such as Amazon S3 or a private web server, allowing multiple Fusion Edge Server instances to obtain their content from the same location.  When the content is updated in the central location, each Fusion Edge Server can automatically update its local content.  The content can even be set to be made available at a specific date and time, meaning each Fusion Edge Server can make the content live at exactly the same time.
+The Fusion Edge Server loads the pre-compiled content into memory on application startup, an Edge Server hosting 18 datasets, with 700k series and 50 million observations will startup and be ready to serve queries in as little as 20 seconds.
 This architecture, has no single point of failure making the Fusion Edge Server the perfect solution for horizontal scaling.

@@ Line 2: / Line 2: @@
 The Fusion Edge Server is a Java web application, it’s responsibility is to host SDMX web services for the dissemination of data and related structural and reference metadata.  The web services support all [https://wiki.sdmxcloud.org/Category:SdmxDataFormat Data Formats] and Structure Formats supported by Fusion Registry as such Fusion Edge Server can be used as a direct replacement for the dissemination services provided by Fusion Registry.
-The purpose of the Fusion Edge Server is to support public or internal dissemination of data and/or metadata either via clients who use the web service API directly, or via software/web user interfaces which convert the information into a graphical display for data discovery, retrieval, and display.  The driver for using Fusion Edge Server as a dissemination solution over Fusion Registry is that Fusion Edge Server offers a read only solution, and with no database it can be horizontally scaled with no single point of failure.
+The purpose of the Fusion Edge Server is to support public or internal dissemination of data and/or metadata either via clients who use the web service API directly, or via software/web user interfaces which convert the information into a graphical display for data discovery, retrieval, and display.  The driver for using Fusion Edge Server as a dissemination solution over Fusion Registry is that Fusion Edge Server offers a read only solution, and with no database it can be horizontally scaled with no single point of failure.  Fusion Edge Server can also work independently of Fusion Registry, there is no requirement to run a Fusion Registry instance, giving options for users who have a requirement to host public SDMX datasets, or who want to offer dynamic access into their data from tools such as Excel, Tableau, or other statistical software.
 Example Applications which make use of these web services are: