Posts on the
Design Decomposition Blog
Cloud Users’ View of Security
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 19, 2013
Changes for IT and Regulatory Requirements
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
Using a Public Cloud instead of an In-House Private Cloud
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
Five Principles for the Incremental SOA Analysis
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
Incremental SOA and Change
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

Transparent persistence in object database products refers to the ability to directly manipulate data stored in a database using an object programming language. This is in contrast to a database sub-language used by embedded SQL or a call interface used by ODBC or JDBC. Using an object database product means that you have higher performance and less code to write. 

With transparent persistence, the manipulation and traversal of persistent objects is performed directly by the object programming language in the same manner as in-memory, non-persistent objects. This is achieved through the use of intelligent caching as this animation shows. For coding examples, see how to access data in an object database. Also see caching for object database management systems.

Transparent persistence

Related Articles

More on the general topic: Object-Oriented Database Management System (OODBMS) Definition

Related Fact Book and Implementation Stories

Douglas K Barry

Read More Free Articles on This Site

There are over 450 pages of articles on this site with over 50 pages on object-oriented database management systems.

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 in Object Databases.

Loading...

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

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.

The intent of this book is to give you an opportunity to consider some ideas and advice that just might make it easier for your organization to realize the potential benefits in Web Services, service-oriented architectures, and cloud computing. No crystal ball exists to tell us the services that will be available tomorrow. Undoubtedly, there will many innovative services that we cannot envision at this time. For that reason, this book presents a straightforward approach that will help you get your organization ready to take advantage of a service-oriented architecture—in whatever form it takes.

"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."


Author, Founder and CTO of Blue Mountain Labs