You might have seen the recent news reports about the collision between U.S. and Russian communication satellites. The U.S. satellite was one of the Iridium satellites. What wasn’t reported and you probably don’t know is that an object database management system (ODBMS) is an important part of the Iridium system. Even though ODBMSs are a [...]
February 13, 2009
I am now also posting on the Cutter Blog. My initial posting is (The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services. It is a response to Anne Thomas Manes’ SOA is Dead; Long Live Services on her blog at the Burton Group.
January 9, 2009
The typical definition of an atomic task or process is one that cannot be decomposed further. This is vague and subject to interpretation. The Decomposition Matrix on this site uses a specific definition: A task (for business process diagrams) or a process (for data flow diagrams) is atomic if every input relates to every output [...]
December 3, 2008
My last posting referenced the criteria for a well-formed business process diagram mentioned in Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. I am going to expand on their criteria to create a more comprehensive definition of a well-formed business process diagram.
To start, here are three criteria from [...]
November 18, 2008
I recently received two new books on business process modeling. Both books looked interesting because they had great titles. As it turns out, one book is great and the other not so good.
The not so good book is Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. There are [...]
October 9, 2008
The Design Decomposition Blog is written by Doug Barry.
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 (new window). For additional
coding examples for transparent persistence, see how
to access data in a relational database (new window).
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 (new
window).
The article's title is "Solving the Java Storage Problem" and it
can be downloaded from the IEEE
Computer site (new window).
There are nearly 400 pages of articles on this site with over 50 pages on object-relational mapping.
Search this site for more articles
Custom Search
Browse this site for more articles
Click on the topics below to browse the articles on this site. You can see more detail by clicking on the arrows. This highlights the location of the current
article: Transparent persistence vs. JDBC call-level interfaces.
Terracotta Upgrades Ehcache InformationWeek Ehcache can also now serve as a caching system for Apache's object-relational mapping system, Hibernate, speeding up its operations. ... and more » 15 Mar 2010 at 8:29am
Browsing Database Artifacts Using Data Source Explorer SYS-CON Media (press release) Generate Object Relational Mappings and Test with EJBQL Oracle Enterprise Pack for Eclipse provides a powerful and flexible object relational mapping ... 4 Mar 2010 at 2:52pm
Even with its success, .NET causes some consternation SDTimes.com The Entity Framework is a broader object-relational mapping framework for .NET. Microsoft denied that internal politics played a role in its decision to ... 10 Mar 2010 at 8:53am
Database Programming with JDBC and Java by George Reese Average Customer Review: based on 40 reviews. Customer Review: The text covers JDBC with enough depth, without burdening the reader with useless details available in any reference (in fact the reference is attached in an appendix, so there is no need to go looking online). Unlike other books it doesn't bore the reader with introduction to obvious concepts and examples. I highly recommend this f...
Beginning Java Databases: JDBC, SQL, J2EE, EJB, JSP, XML by Kevin Mukhar, Todd Lauinger, John Carnell Average Customer Review: based on 7 reviews. Customer Review: I'm using this book as my text book for my independent study of database programming with Java. This book is the tops! The primary focus is programming with the Cloudscape database, but it does give you code snippets to use if you're using Oracle or one of the Microsoft databases (like SQL Server). What impresses me about the book is...
JDBC(TM) API Tutorial and Reference: Universal Data Access for the Java(TM) 2 Platform (2nd Edition) by Seth White, Maydene Fisher, Rick Cattell, Graham Hamilton, Mark Hapner Average Customer Review: based on 22 reviews. Customer Review: JDBC is one of the most mature and widely used Java APIs. Even after the arrival of more recent tools and technologies like EJB's CMP and JDO, JDBC still remains a simple, fast, and reliable way of storing objects' state in an RDBMS. While conceptually this technology is quite straightforward, its evolution has made it more complex ...