The topic of Java Object Persistence is as actual as ever…<\/p>\n
I have therefore interviewed together with InfoQ.com’s Floyd Marinescu the following group of leading persistence solution architects on their views on the current State of the Union of object persistence with respect to Java:<\/p>\n
Mike Keith: EJB co-spec lead, main architect of Oracle Toplink ORM<\/p>\n
Ted Neward: Independent consultant, often blogging on ORM and persistence topics<\/p>\n
Carl Rosenberger: lead architect of db4objects, open source embeddable object database<\/p>\n
Craig Russell: Spec lead of Java Data Objects (JDO) JSR, architect of entity bean engine in Sun’s appservers prior to Glassfish<\/p>\n
Here are the questions at a glance:<\/p>\n
Question 1: Do we still have an “impedance mismatch problem”?<\/p>\n
Question 2: In terms of what you’re seeing used in the industry, how would you position the various options available for persistence for new projects?<\/p>\n
Question 3: What are in your opinion the pros and cons of these existing solutions?<\/p>\n
Question 4: Do you believe that Object Relational Mappers are a suitable solution to the “object persistence” problem? If yes why? If not, why?<\/p>\n
Question 5: Do you believe that Relational Database systems are a suitable solution to the “object persistence” problem? If yes why? If not, why?<\/p>\n
Question 6: Do you believe that Object Database systems are a suitable solution to the “object persistence” problem? If yes why? If not, why?<\/p>\n
Question 7: What would you wish as a new research\/development in the area of Object Persistence in the next 12 months?<\/p>\n
Question 8: If you were all powerful and could have influenced technology adoption in the last 10 years, what would today’s typical project use as a persistence mechanism and why?<\/p>\n
Question 9: Any parting words about this topic?<\/p>\n
The answers we got differ, but I believe all panelists agree that there is no silver bullet….<\/p>\n