Difference between revisions of "SDI-Service"
(→Philosophy) |
(→Architecture) |
||
| Line 20: | Line 20: | ||
=== Architecture=== | === Architecture=== | ||
| − | + | The picture below describes the overall architecture of gCube SDI and the interaction between its components. The SDI-service manages all instances across contexts, allowing for a better control of policies, and acting as gateway for SDI configuration retrieval. | |
| + | [[Image:SDI_Service_Architecture.png|frame|center|SDI Architecture]] | ||
== Deployment == | == Deployment == | ||
Revision as of 14:23, 9 June 2017
Contents
Overview
The SDI-Service is a REST gCube service that acts as main control point for the entire SDI. It handles configuration of geo-services, while providing simple APIs to interact with it. This document outlines the design rationale, key features, and high-level architecture, the options for their deployment and as well some use cases.
Key features
SDI-Service is a REST service offering the following key features:
- SDI Configuration management
- APIs to easily query the IS and the SDI's geo-services configuration details
- APIs to configure geo-services through the infrastructure contexts
- GeoSpatial datasets management
- APIs to publish both data and metadata into the SDI
Design
Philosophy
SDI facilities are prominent features in data infrastructures, and they must serve heterogeneous needs. In order to keep control of the SDI over the infrastructure, the SDI-Service acts as a central point of interaction for applications. The choice of REST API has been made in order promote its interoperability across applications implementation.
Architecture
The picture below describes the overall architecture of gCube SDI and the interaction between its components. The SDI-service manages all instances across contexts, allowing for a better control of policies, and acting as gateway for SDI configuration retrieval.
