Difference between revisions of "Biodiversity Access"
Lucio.lelii (Talk | contribs) m (→Design) |
Lucio.lelii (Talk | contribs) m (→Philosophy) |
||
Line 15: | Line 15: | ||
=== Philosophy === | === Philosophy === | ||
+ | Handling heterogeneous biodiversity repositories with different capabilities and dissimilar results modeling is one of the main goals for biodiversity studies. | ||
+ | This subsystem offer the possibility to retrieve, to manage and to elaborate all this data with a single entry point. | ||
+ | The choice to not use the tree-manager subsystem was taken | ||
=== Architecture === | === Architecture === |
Revision as of 15:55, 27 February 2012
A cluster of components that allows uniform access over different biodiversity repositories.
This document outlines their design rationale, key features, and high-level architecture as well as the options for their deployment.
Contents
Overview
The goal of this subsystem is to offer an uniform access over different biodiversity repositories through a simple API. The services have dynamically extensible architectures, i.e. rely on independently developed plugins to adapt their APIs to a variety of back-ends within or outside the system. When connected to remote data sources, the services may be widely replicated and their replicas know how to leverage the Enabling Services to scale horizontally to the capacity of the remote back-ends.
Design
Philosophy
Handling heterogeneous biodiversity repositories with different capabilities and dissimilar results modeling is one of the main goals for biodiversity studies. This subsystem offer the possibility to retrieve, to manage and to elaborate all this data with a single entry point. The choice to not use the tree-manager subsystem was taken