...
- In order to scale up effectively, will need to be able to add compute capacity and distribute load with load balancing. This suggests that clustering of the Fedora instances will be required.
- In order to be able to add and remove compute capacity efficiently, the storage of assets must be in a persistent store outside of the compute resources.
- A shared persistent store is preferred, so that once a file is written, it is available to all other instances in the cluster without having to be written again at each node.
- The obvious shared persistent store in the AWS environment (where the Hydra-in-a-box hosted service will be deployed) is S3.
- Storage of files through Fedora going to S3 suggests the need for a ModeShape binary store implementation for S3.
- The object metadata of Fedora will be written to a relational database for ease of querying and performance and because Modeshape only supports using a relational database as the object storage location in a cluster
...