Jul 9th, 2012, 12:21 PM
Support JPA _or_ NOSQL at runtime?
I am rewriting a .Net-based web application into a Java application and have selected Spring for my target framework. I have already gone through some POC scenarios internally and with some external potential and existing customers. I see the benefit of the object DB for a default implementation and for sites that do not state a preference. I have , however, had push back from both the existing and the potential customers regarding an object database backing the database. These organizations either may do have the IT infrastructure that understands how to implement effective backup and maintenance of object DBs or already have RDBMS infrastructure in place that the the product simply ties into.
I am looking for a way to try to generically write my data access layer to support both JPA and NoSQL (Neo4J) simultaneously. It would be up to the deployment to determine what DB to use.
I have found samples for performing polyglot storage but none that would allow me to abstract the domain object from the storage mechanism at the object/rdbms level (based on the documented annotations I have read).
Anyone have any thoughts or recommendations for achieving this goal?
Tags for this Thread