{"id":79,"date":"2008-05-15T22:09:00","date_gmt":"2008-05-15T22:09:00","guid":{"rendered":"http:\/\/www.odbms.org\/odbmsblog\/2008\/05\/15\/java-object-persistence-state-of-the-union-part-ii-published\/"},"modified":"2008-05-15T22:09:00","modified_gmt":"2008-05-15T22:09:00","slug":"java-object-persistence-state-of-union","status":"publish","type":"post","link":"https:\/\/www.odbms.org\/blog\/2008\/05\/java-object-persistence-state-of-union\/","title":{"rendered":"Java Object Persistence: State of the Union PART II Published"},"content":{"rendered":"

More on the topic of Java Object Persistence …
\nI have this time interviewed the following ODBMS.ORG experts Jose Blakeley (Microsoft)<\/a>, Rick Cattell (Sun Microsystems)<\/a>, William Cook (University of Texas at Austin)<\/a>, Robert Green (Versant)<\/a> , and Alan Santos (Progress)<\/a>.<\/p>\n

The panel addressed the ever open issue of the impedance mismatch, a problem which has existed ever since computers were used to persistently store data – in file systems or database management systems -, and where no fully satisfactory solutions have been found as of yet.<\/p>\n

The complete panel transcript is available for free download (PDF)<\/a><\/p>\n

“Today, I see two types of impedance mismatch problems,” says Jose Blakeley, a Partner Architect in the SQL Server Division at Microsoft. “(1) the application’s impedance mismatch problem, and (2) the impedance mismatch in data services.”<\/p>\n

Alan Santos from data integration specialist Progress Software takes a different view: “Historically impedance mismatch has referred to the issues encountered when mapping data from a relational store into an object oriented data model. For some people, in some very practical ways, impedance mismatch is not an issue and has been solved with improvements in O\/R mapping libraries and performance improvements in the runtime environments, as well as hardware itself.”<\/p>\n

Rick Cattell, formerly Distinguished Engineer at Sun Microsystems who has been instrumental in the foundation of J2EE, SQL Access\/ODBC and JDBC, sees three solutions to overcome the mismatch: “The top three options for Java are JDBC, O\/R mapping, and an ODBMS.”<\/p>\n

But panelists differed when asked about their views on whether object-relational mappers, relational databases and object databases were a suitable solution to the “object persistence” problem.<\/p>\n

The panel also attempted to define new areas of research and development in object persistence.<\/p>\n

Microsoft’s Blakeley: “I would like to see technologies like the EDM, EntitySQL, and EF be absorbed natively by relational database systems.”<\/p>\n

UT Austin’s William Cook, a father of Apple Script, Safe and Native Queries agreed and wished that “major database vendors implement OQL (or some variant, like HQL) as a native database interface to their databases.”<\/p>\n

I reccomend it, it is a very informative readings!<\/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

##<\/p>\n","protected":false},"excerpt":{"rendered":"

More on the topic of Java Object Persistence … I have this time interviewed the following ODBMS.ORG experts Jose Blakeley (Microsoft), Rick Cattell (Sun Microsystems), William Cook (University of Texas at Austin), Robert Green (Versant) , and Alan Santos (Progress). The panel addressed the ever open issue of the impedance mismatch, a problem which has […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[298,300,418],"_links":{"self":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/posts\/79"}],"collection":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/comments?post=79"}],"version-history":[{"count":0,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/posts\/79\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/media?parent=79"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/categories?post=79"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/tags?post=79"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}