search

EOEPCA / use-case-analysis

Use Cases Analysis Document
https://eoepca.github.io/use-case-analysis/
Apache License 2.0
1 stars 0 forks source link

Data storage and access #4

Open ivothecat opened 5 years ago

ivothecat commented 5 years ago

Due to strategic or other internal constraints, service providers might need to consider or be willing to adopt a variety of storage options for the resources they intend to share via the EO exploitation platform. For example, infrequently accessed data / resources might be moved or stored in cheaper storage options that normally come with longer retrieval times. It would be useful if the expectation / requirement around the adoption of different data storage options and data retrieval / access could be expanded in more detail.

Thank you Ivo

rconway commented 5 years ago

See section Data Access Gateway of the design document - https://eoepca.github.io/master-system-design/#mainDataAccessGateway. We have a general understanding that the storage / data-access interface of the hosting infrastructure is heterogeneous. Thus, we try to present 'internally' a normalised storage interface that is abstracted from the underlying protocols etc. This facilitates provision of re-usable components that can rely upon the abstraction and so be deployed to different platforms with heterogeneous back-end offerings. For this to work an appropriate abstraction layer must be deployed within the infrastructure - which may have to be bespoke developed, or maybe based on one that already exists.