Oct. 9, 2018 06:00 AM EDT
| By ODBMS Industry Watch | Article Rating: |
|
| May 16, 2008 01:09 AM EDT | Reads: |
260 |
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 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.
The complete panel transcript is available for free download (PDF)
"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."
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."
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."
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.
The panel also attempted to define new areas of research and development in object persistence.
Microsoft's Blakeley: "I would like to see technologies like the EDM, EntitySQL, and EF be absorbed natively by relational database systems."
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."
I reccomend it, it is a very informative readings!
Here are the questions at a glance:
Question 1: Do we still have an "impedance mismatch problem"?
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?
Question 3: What are in your opinion the pros and cons of these existing solutions?
Question 4: Do you believe that Object Relational Mappers are a suitable solution to the "object persistence" problem? If yes why? If not, why?
Question 5: Do you believe that Relational Database systems are a suitable solution to the "object persistence" problem? If yes why? If not, why?
Question 6: Do you believe that Object Database systems are a suitable solution to the "object persistence" problem? If yes why? If not, why?
Question 7: What would you wish as a new research/development in the area of Object Persistence in the next 12 months?
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?
Question 9: Any parting words about this topic?
##
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 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.
The complete panel transcript is available for free download (PDF)
"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."
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."
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."
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.
The panel also attempted to define new areas of research and development in object persistence.
Microsoft's Blakeley: "I would like to see technologies like the EDM, EntitySQL, and EF be absorbed natively by relational database systems."
CIO, CTO & Developer Resources
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."
I reccomend it, it is a very informative readings!
Here are the questions at a glance:
Question 1: Do we still have an "impedance mismatch problem"?
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?
Question 3: What are in your opinion the pros and cons of these existing solutions?
Question 4: Do you believe that Object Relational Mappers are a suitable solution to the "object persistence" problem? If yes why? If not, why?
Question 5: Do you believe that Relational Database systems are a suitable solution to the "object persistence" problem? If yes why? If not, why?
Question 6: Do you believe that Object Database systems are a suitable solution to the "object persistence" problem? If yes why? If not, why?
Question 7: What would you wish as a new research/development in the area of Object Persistence in the next 12 months?
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?
Question 9: Any parting words about this topic?
##
Read the original blog entry...
Published May 16, 2008 Reads 260
Copyright © 2008 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
IoT & Smart Cities Stories
By Pat Romanski Oct. 9, 2018 01:00 AM EDT Reads: 1,658 |
By Yeshim Deniz Oct. 8, 2018 07:00 AM EDT Reads: 3,665 |
By Liz McMillan Oct. 8, 2018 05:45 AM EDT Reads: 2,839 |
By Pat Romanski Oct. 8, 2018 01:15 AM EDT Reads: 3,205 |
By Pat Romanski Oct. 6, 2018 10:45 PM EDT Reads: 3,116 |
By Liz McMillan Oct. 6, 2018 11:45 AM EDT Reads: 2,979 |
By Pat Romanski Oct. 5, 2018 09:00 PM EDT Reads: 1,727 |
By Yeshim Deniz Oct. 3, 2018 01:00 PM EDT Reads: 3,210 |
By Zakia Bouachraoui Sep. 6, 2018 07:30 PM EDT |



Most modern computer languages embed a lot of metadata in their application. We show how this goldmine of data from a runtime environment like production or staging can be used to increase profits. Adi conceptualized the Crosscode platform after spending over 25 years working for large enterprise companies like HP, Cisco, IBM, UHG and personally experiencing the challenges that prevent companies from quickly making changes to their technology, due to the complexity of their enterprise. An accomplished expert in Enterprise Architecture, Adi has also served as CxO advisor to numerous Fortune executives.
Cloud computing is a goal aspired to by all organizations, yet those in regulated industries and many public sector organizations are challenged in adopting cloud technologies. The ability to use modern application development capabilities such as containers, serverless computing, platform-based services, IoT and others are potentially of great benefit for these organizations but doing so in a public cloud-consistent way is the challenge.
"Calligo is a cloud service provider with data privacy at the heart of what we do. We are a typical Infrastructure as a Service cloud provider but it's been des...
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the...
Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term.
A total of 88% of Fortune 500 companies from a generation ago are now out of business. Only 12% still survive. Similar percentages are found throughout enterprises of all sizes.
We are offering early bird savings on all ticket types where you can save significant amount of money by purchasing your conference ti...
According to Forrester Research, every business will become either a digital predator or digital prey by 2020. To avoid demise, organization...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine f...














