I ran into an Issue of implementing an object store using Apache EmpireDB https://issues.apache.org/jira/browse/ISIS-222 which triggered me to share my thoughts on object stores.
I definitely don't want to stop intentions to implement more object stores within Isis but personally I prefer the use of a standards compliant Java API like JPA or JDO and select an implementation with an Apache2 license (OpenJPA, Datanucleus) as a reference. It's future proof and users can replace it with a different provider if they need better performance or, in the case of JDO, exotic object stores. Also we can rely on other communities to maintain the various implementations and providers. When choosing between JPA and JDO I found some interesting stuff, looks too me that JPA is targeted solely to RDBMS: http://www.datanucleus.org/products/accessplatform/jdo_jpa_faq.html http://db.apache.org/jdo/jdo_v_jpa.html If our goal is to have a type-safe API (I'm a big fan of string free coding) then QueryDSL (JPA, JDO) or DataNucleus (JDO) could be added to the mix: http://datanucleus.blogspot.com/2010/11/jdo-typesafe-vs-jpa-criteria.html http://www.querydsl.com/modules I'm interested your thoughts on this. Kind Regards, Jeroen van der Wal
