For a variety of reasons, our application requires direct access to a filesystem in order to perform some of its functionality. These areas include data storage (we use a graph model database for part of our application), dynamically loading and deploying Jars/bundles at runtime, and storage of large blob/clob data. While some of these could be virtualized to an RDBMS or JPA store, it would be very suboptimal in terms of performance. Also, for the dynamic jar loading, we definitely need some type of file system access (or would have to write a custom classloader and splice it into the classloader hiearchy, which brings with it a whole host of other concerns).
On AWS, for example, we attach an EBS volume to each instance as its backing file system store and mount it to a known location/path on the VM. There does not seem to be similar capability in NetWeaver cloud.
Anyone have any insights on how these limitations can be worked around?
Thanks!
Rick
