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 [...]
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 [...]
October 9, 2008
The Design Decomposition Blog is written by Doug Barry.
Because an ODBMS stores exactly the same object model that is used at the
application level, both development and maintenance costs can be reduced. With
an ODBMS, there is no need to:
Develop two data models: an object model in the
application and a relational model stored in the database. This is not
needed because an ODBMS uses the same object model as the application.
Maintain two data models. An ODBMS eliminates the
maintenance cost of keeping the to data models synchronized.
Develop mapping between the relational and the object
models. This is not needed because an ODBMS uses the same object model
as the application.
Maintain the mapping between the relational and object
models. An ODBMS eliminates the maintenance cost of maintaining the
mapping whenever there is a change to the object or relational model.
The result is that for a development team of six to seven, it is possible to
have a team with one less person when using an ODBMS. It is typical when
developing an object application with a RDBMS that one person is in charge of
keeping the relational model synchronized with an object model and the mapping
code. That person would not be needed in an ODBMS development project.
There are nearly 400 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: One model to reduce development and maintenance costs.
Related recent articles from Google News
Of Earth and Beyond: Bonny Doon Winery CHS Capitol Hill Seattle Randall can boast some interesting things, such as being one of the only living winemakers to have an asteroid named after him: JPL Small Object database item #4934, “Rhoneranger.” It has an orbital period of 5.2 years. Randall also has downsized his ... 2 Feb 2012 at 4:50pm
PostgreSQL flies into the cloud ITworld.com Storage engine vendors, for instance, are shying away from MySQL as an object database engine because it would require them to enter into an contract relationship with MySQL's current owner Oracle--a company with which they directly compete. and more » 25 Jan 2012 at 9:33am
C++ Object Databases: Programming with the ODMG Standard by David Jordan Description: In 1991, the Object Database Management Group (ODMG) was formed to define standard interfaces for object databases. This standardization has since been achieved, and the popularity of object databases is on the rise. Similar to using SQL to access a relational database, the ODMG provides a corresponding standard for object databases. This book, technically reviewed by ODMG members,...
Succeeding with Object Databases: A Practical Look at Today's Implementations with Java and XML by Akmal B. Chaudhri, Roberto Zicari Description: Take a tour with leading researchers and developers for a practical look at object databases. Whether you currently work with or are thinking of moving to object databases, Chaudhri and Zicari provide a collection of real-world case studies and examples that demonstrate how some of the world's leading companies and research institutions are leveraging Java, XML, and Object Relation...
The Object-Oriented Enterprise: Making Corporate Information Systems Work (Database Experts) by Rob Mattison, Michael J. Sipolt Description: Object technology is widely used in database management systems, but few details on its practical application to business are available. This step-by-step guide shows how to create, maintain and manage object-oriented database applications in a corporate environment. This reference covers the fundamental building blocks of object-oriented databases, detailing how they work and how ...
