Writing your own mapping layer |
|
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:
Read more free articles on this siteThere 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 articlesClick on the topics below to browse the articles on this site.The arrows show the path to the current article: Writing your own mapping layer.
Related recent articles from Google News
More related news: "object-relational mapping" - Google News Related books at Amazon.com
More related books: Search Amazon.com for object relational mapping
Copyright © 2000-2009 Barry & Associates,
Inc. All Rights Reserved.
|
|
|