What are the consequences (or issues that I might face) if I try to hack Xodus File I/O, as such I will use ByteBuddy to replace all access to Java File I/O and that Xodus will actually "persist" to that interface instead of the disk I/O, since I find it inefficient (and almost impossible) to have persistent storage on cloud platforms (Heroku, Openshift to names a few)--so this hack I am thinking is to create my own Java File I/O that instead of saving to disk it will save to a more elastic storage, such as Google Cloud Storage, S3 and other Object storage. So that I can run my app in Heroku or Openshift.
Will there be a side-effect with Xodus if I replace the File I/O with ByteBuddy or Xodus database is agnostic about it?