Transparent Persistence vs. JDBC Call-Level Interfaces

In November 1998, Torsten Stanienda and I wrote an article for IEEE Computer that compared transparent persistence to a call-level interface. The article was based on an exercise Torsten did that compared the ODMG transparent persistence for Java to the JDBC call-level interface. Even though the article goes back some years, the results of Torsten's exercise are worth noting.

Torsten created an example set of classes for Person, Professor, Student, Course, and LectureRoom. He then wrote two sets of code to create, access, and manipulate objects in each of the classes. One set of code used the ODMG Java Binding and the other used the JDBC call-level interface. A summary of the results are shown in the graph below. For this exercise, 496 lines of code were needed using the ODMG Java Binding compared to 1,923 lines of code using JDBC.

What does this mean for you? Granted this is small example, but it does demonstrate the difference in the lines of code needed between transparent persistence and a call-level interface. This can be an advantage when it comes to development costs. The results can be extrapolated to Java Data Objects (JDO) or the ODMG C++ Binding. See transparent persistence. For additional coding examples for transparent persistence, see how to access data in a relational database .

Note that this example does not cover the development time needed to design the best mapping when using an object-relational mapping product. It also does not cover entering this information into the object-relational mapping product so that the mapping layer can be generated. Nevertheless, using transparent persistence with an object-relational mapping products significantly reduces development time. See development costs with object-relational mapping products.

The article's title is "Solving the Java Storage Problem" and it can be downloaded from the IEEE Computer site.

JDBC transparent persistence JDO advantage

Related Articles

More on the general topic: Object-Relational Mapping (OR Mapping) Definition

Related Fact Book

You may use this material for your work or classes. Reprint Policy. Be sure to check the menu at the left for other articles available on this site.

The Savvy Manager's Guide

Douglas K Barry is also the author of a book that explains Web Services, service-oriented architecture, and Cloud Computing in an easy-to-understand, non-technical manner.

Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide

Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide (Second Edition)

by with David Dick

This is a guide for the savvy manager who wants to capitalize on the wave of change that is occurring with Web Services, service-oriented architecture, and—more recently—Cloud Computing. The changes wrought by these technologies will require both a basic grasp of the technologies and an effective way to deal with how these changes will affect the people who build and use the systems in our organizations. This book covers both issues. Managers at all levels of all organizations must be aware of both the changes that we are now seeing and ways to deal with issues created by those changes.