Difference between revisions of "TimeSeries"

From Gcube Wiki
Jump to: navigation, search
(Deployment)
(Use Cases)
Line 41: Line 41:
  
 
=== Well suited Use Cases ===
 
=== Well suited Use Cases ===
 +
 +
The Service is particularly suited to support process on large dataset of timeseries and to collect statistics on such data.
  
 
== Subsystems ==
 
== Subsystems ==

Revision as of 16:43, 11 May 2012

A service for performing assessment and harmonization on time series. The aim is to provide users with an interface and methods for assessing if values are not correct, for linking with codelists (for a better managing) or for performing some processing and aggregation on such data. This document outlines the design rationale, key features, and high-level architecture, as well as the options deployment.

Overview

The goal of this service is to offer a single entry for processing, assessing and harmonizing time series.

The service is able to import data using different protocols.

Design

Philosophy

This represents an endpoint for users who want to process time series in order to extract informations.

Architecture

The subsystem comprises the following components:

  • TimeSeries service: the service core;
  • TimeSeries client library: a library to connect to the service.

A diagram of the relationships between these components is reported in the following figure:

TimeSeries service Architecture

Deployment

All the components of the service must be deployed together in a single node. This subsystem can be replicated on multiple hosts and scopes, this does not guarantee a performance improvement because this is associated to the requests which are made towards the database.

Small deployment

The deployment follows the schema of the Architecture

Use Cases

Well suited Use Cases

The Service is particularly suited to support process on large dataset of timeseries and to collect statistics on such data.

Subsystems