RDC Integration
Overview
Getting started
User Guide
Basically, AOS is intended as a data backend for the RDC. For this reason, very few end users will use AOS directly. Data import, verification, transformation and processing is basically possible via the services in the mediation layer. This also ensures the consistency of the data. Users and services can be informed about changes to individual data objects or even entire projects via the AOS notification service and can thus react to these changes.
Developer Guide
The current documentation for using AOS is linked from the AOS home page at https://aruna-storage.org. This contains a complete description of the API. AOS consists of four main components: AOS Server, AOS Proxy, AOS API (and its S3 interface), AOS CLI, and AOS Notification System. Of these, the servers with the database system behind them are installed and administered by the AOS team. AOS proxies can then be installed at various locations, which then communicate with the servers in each case. The actual data traffic from and to the storage backend then takes place via the AOS proxies. The interaction between a client and the proxies/servers takes place via the AOS API. To reduce the entry barrier, there is a command line interface in the form of the AOS CLI, which encapsulates API calls. Moreover, an S3 interface was implemented, due to many software already supports data storage via S3 as industry standard. Finally, the AOS notification system will be released soon. This will make it possible to react to changes in the AOS. This can be, for example, a data verification that is automatically initiated when a data upload is complete.
References
Links:
- Dokumentation and Aruna start page: https://aruna-storage.org
- Source-Code: https://github.com/ArunaStorage