Data Discovery/Server Discovery Service Implementation

As expressed in SP-3000 , there is currently no clear way forward to prevent latency of the visualisation of big data cubes within the SRC Net data lake. As these files could be in different repositories, a preliminary data cube transfer (or stream) where the parser server is located (usually, tools use a client-server architecture to parse big files) could produce a high-latency starting phase to start the visualisation and, also, provide a possible resources problem in the cache storage area and a network use A discovery service could prevent this movement, allowing remote operations where the data is located. The real implementation of the service allows a dynamic identification of tool servers (if a new server is deployed, it will be offered for connections) and, also, it will allow future extensions to cover high-availability and load-balance features (offering the best parser server at every time)