Impedance mismatch when mapping from a relational database

Posts on the
Design Decomposition Blog

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

(The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services

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

Atomicity

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

Well-Formed Business Process Diagrams

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

Recent Business Process Modeling Books

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.

Impedance mismatch occurs when you need to map objects used in an application to tables stored in a relational database. This mapping is illustrated in the figure below. Mapping objects to tables and vice versa creates a performance disadvantage when you have complex data. For mapping details, see mapping. Also see complex data (new window).

Impedance mismatch disadvantages

More on the general topic: No impedance mismatch

Mapping

Copyright © 2000-2010 Barry & Associates, Inc. All Rights Reserved.
You can use this material for your work or classes. Click here for our reprint policy.

Related books at Amazon.com

Object-Oriented Database Design Clearly Explained
by Jan L. Harrington
Average Customer Review:

based on 7 reviews.
Customer Review: "Object Oriented Database Design" is a book for beginners and, as far as I have been able to investigate, it is a perfect walkthrough along the background of object structures. Figures, exemples, syntax of codes and clear explanations lead the learner through theory towards practice. Exemples are often very nice.

Moving Objects Databases (The Morgan Kaufmann Series in Data Management Systems)
by Ralf Hartmut Güting; Markus Schneider
Publisher: Morgan Kaufmann
Publication Date: August 2005

Learning PHP Data Objects: A Beginner's Guide to PHP Data Objects, Database Connection Abstraction Library for PHP 5
by Dennis Popel
Average Customer Review:

based on 5 reviews.
Customer Review: I like the book's erudite methodology. The methodology of this book is based on the two tenets of sound education: Informing Demonstrating In this books after the information I found lots of exercises, step by step, with plenty of pictures and screen shots that lead me through and demonstrated a process of task. These exercises are f...

More related books: Search Amazon.com for object database

Impedance mismatch when mapping from a relational database

Read more free articles on this site

Search this site for more articles

Browse this site for more articles

Related recent articles from Google News

Related books at Amazon.com