Newletter Sign Up
Posts on the
Design Decomposition Blog
Iridium Satellite Collision in Space
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.

It can be very tempting to write your own object-relational mapping. If fact, there are books and articles advocating this. The bottom line, however, is that unless you have a very simple mapping, it is a bad idea to write your own mapping layer.

I have talked with plenty of developers who tried writing a mapping layer. The result, although anecdotal, is universal. The mapping code, in each case, grew to be 30 to 40 percent of the code needed for the entire application. There are two problems that resulted from this. The first is that this is a lot of effort towards writing code that is not addressing the business problem that prompted the application development in the first place. The second is that, given the development models that show how code defects rise with total code, a significant number of additional defects appeared which, again, are not directly related to the business problem being addressed by the application development.

So, if you have a relational database and you want to use C++ or Java, by all means use an object-relational product. Writing a mapping layer is much harder than you might expect. Some of the reasons this is hard can be seen in the considerations for mapping:

Related content for: Writing your own mapping layer

More on the general topic: Object-relational mapping articles

Read more free articles on this site

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: Writing your own mapping layer.

Loading...

Related recent articles from Google News

ZK with Non-relational Database mongoDB
TheServerSide.com
Typically, for relational databases developers either use plain JDBC or some sophisticated object-relational mapping library like Hibernate. This series of small talk will show how developers can develop non-relational database driven ZK applications.

26 Jan 2012 at 1:42pm
NoSQL NewSQL以及其他数据库编程语言
移动Labs
Good bye object-relational mapping. New information management solutions are rapidly being adopted even by large corporations, for instance Nick Tan, from the Commonwealth Bank of Australia ...

17 Jan 2012 at 6:59pm
Doctrine 2 e Zend Framework 2, un esempio di combinazione vincente
Programmazione.it
Per chi quindi volesse avvalersi di tecniche ORM (Object Relational Mapping) per la propria applicazione basata su Zend Framework non resta che affidarsi a strumenti come Doctrine, cercando di ottenere una sana e proficua convivenza tra i due framework ...

30 Jan 2012 at 11:28pm
More related news on: "object-relational mapping"

Related books at Amazon.com

Databases: Database, Relational database, Relational model, Database management system, Database normalization, Object-relational mapping
Databases: Database, Relational database, Relational model, Database management system, Database normalization, Object-relational mapping
by Source: Wikipedia
Description: Please note that the content of this book primarily consists of articles available from Wikipedia or other free sources online. Pages: 215. Chapters: Database, Relational database, Relational model, Database management system, Database normalization, Object-relational mapping, IBM Lotus Notes, Distributed database, Weak entity, Set domain, Open Database Connectivity, Commitment ord...
More related books: Search Amazon.com for object-relational mapping