This post picks up on two ideas in my last post. The first idea is that IT will have significant change, in part, from the adoption of Cloud Computing. Take a look at IT Departments Won’t Exist in Five Years at Computerworld.com. It states that: Consumerization of IT and self-service trends will lead to a [...]
June 12, 2013
Two recent surveys (details below) support the driving and restraining forces related to security shown in the Force Field Analysis for Using a Public Cloud instead of an In-House Private Cloud posted a couple weeks ago. Participants in both surveys were Cloud users. Data supporting the driving forces: The TechInsights Report 2013: Cloud Succeeds stated [...]
June 9, 2013
Last April, Jason Bloomberg of ZapThink issued a ZapFlash titled Cloud Computing: Rethinking Control of IT. I thought it would be useful to organize his arguments into a Force Field Analysis as described in Web Services, Service-Oriented Architectures, and Cloud Computing. The following analysis also includes information from two other ZapFlash entries that Jason referenced [...]
June 5, 2013
After last week’s posting, I thought I should say more about incremental SOA analysis. The following is from Chapter 10 in Web Services, Service-Oriented Architectures, and Cloud Computing. Service-oriented architecture (SOA) projects are no different from other IT projects in that larger projects tend to fail and issues regarding change can scuttle projects. This chapter [...]
May 29, 2013
Computerworld had an article last January that discussed American Airlines’ approach to using Web Services and multiple enterprise service buses (ESBs) as part of their service-oriented architecture (SOA). The authors emphasized a change from build vs. buy and from using mainframes. That, however, is not the part I found interesting. (Also, several comments to the [...]
May 22, 2013
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
There are over 450 pages of articles on this site with over 50 pages on object-relational mapping.
Search this site for more articles
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.
The Savvy Manager's Guide
Douglas K Barry has prepared the material on this site. He 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 (Second Edition)
by Douglas K Barry with David Dick
One of the toughest jobs for managers today is keeping up with the rapid changes in technology. An important change in technology is that the future of software will involve service-oriented architectures with some form of cloud computing. More and more services are available on the Internet. Nearly every day, we can discover new opportunities to connect these services together to create service-oriented architectures (SOAs). These SOAs will require less custom software in organizations, but will likely demand more creativity in the selection and assembly of services. This is a natural evolution of software technology and will be explained in this book.
This is a non-technical book on a technical subject. It assumes no prior knowledge of the technology. It is written with a high-level view at the beginning of the book. As the book progresses, technical details are introduced and explained. You can stop reading at any point once you have enough understanding for your use.
"Web Services, Service-Oriented Architectures, and Cloud Computing by Douglas Barry provides easy-to-follow guidance around the proper use of web services, how they exist within SOA, and how the emerging use of cloud computing correctly fits into the mix. This is something that most in this industry can neither define nor implement, and getting it right the first time is critical to success. If you're looking to understand the true nature of web services, SOA, and cloud computing—including the underlying details—then you should begin by reading this book."