I’m working in a company that is using NetCDF4 and HDF5 files for exporting datasets from our LIDAR and RADAR type of devices and data processing systems. I’m currently evaluating if HSDS can be used to provide a new and smarter API for datasets compared to files. Based on HSDS documentation and a brief hands-on evaluation, HSDS looks very interesting. I have visioned perhaps 3 different of use cases for us:
Devices-to-cloud: A device buffers measurement data locally and creates slices of datasets. Slices are then send to a data processing system which is running in the cloud and provides a HSDS REST API for the device.
In-cloud: The cloud based data processing system contains micro services that each read slices of a dataset, processes data and then writes slices back by using HSDS REST API.
Cloud-to-application: A visualization application in browser or backend uses HSDS REST API to read slices based on various criteria e.g. bounding boxes, time window, customer id etc.
Q1: I want opinions if these super-high-level use cases are practical with HSDS?
Q2: An another concern is the current maturity level of HSDS. The latest version is 0.6-beta and maybe it is too early to use it for production level systems/APIs that our customers are paying for, or how do you feel?
Q3: Is there a HSDS release roadmap that would give a vision what can be expected to happen in HSDS development in the coming years?