Blog
Saturday, August 13, 2011
Why use an ORM?
Object/Relational Mapping, or ORM for short, tools are becoming more and more popular among web and application developers. In my experience I've noticed three main reasons why so many developers are jumping on the band wagon of ORM based data access layers.

1.) Speeds up development time

Simply put, custom data access projects can take hundreds, if not thousands, of hours to develop. And that's just for the initial setup. Then there's the never ending maintenance and (most likely) futile attempts to keep the project using the most modern technologies. On the other hand all of the ORM tools I have worked with to date have had the ability to instantly build data object models based on existing database schemas. Most can even do the reverse; build (and maintain) an entire database model from an existing data object code layer. ORMs accomplish this task in minutes, not days or weeks like traditional. Meaning that with just a few clicks of a mouse your system will already have the back bone to any data access layer; CRUD (Create, Read, Update, Delete) operations. Combine all of that with the fact that there's a squadron of hot pocket eating and World of Warcraft LiveWire Mountain Dew drinking nerds out there, that at this very instant are doing all that is necessary to keep that their ORM software up to date and bug free.

2.) Increased efficiency and performance

"Whoa, hold up, dawg! Did he just use the words "increased, "efficiency", and "performance" while referring to an ORM?"

I know what you're thinking. "ORMs pump out good, generic code. However, I pump out great, customized code." Wrong. However, even if you're right consider this; an average development team has varying levels of expertise and experience. Every team member isn't . As a result, they may not follow design patterns in their code, and end up with a sub par quality of code that leads to increased maintenance and poorer performance. Throw in the fact that with multiple developers writing code comes increased inconsistency, which in turn means increased maintenance. On top of all of that most development shops aren't in the business of creating world-class data access layers. It's merely a means to an end. ORMs are in that business, and it shows.

3.) The sky's the limit

ORMs take care of most, if not all, of the data management and object persistence (stateless) handling from the very beginning. This is incredibly beneficial, because as I mentioned before most development teams have a broad range of experience among members. ORM tools thrive in this type of environment, because they take the heat off of less experienced developers in regards to data management while still allowing a high level of customization from more skilled team members.


ORM tools I've used:
ORM resources I like:
0 Comments  |  Add Comment
Rss Subscribe Facebook Twitter
© 2011 NetDuo Creative, LLC | Privacy Policy