I Just Don't Like Object Mappers

home
database
view story

3 Kicks

I Just Don't Like Object Mappers(openmymind.net)

submitted by Noldorin(829) 6 months, 4 days ago

Karl Seguin also discusses the use of Object Relational Mappers, and Data Mappers and how he has a growing dislike of them.

2 comments |category: Database |Views: 90
Tweet

tags: Database another

Everyones tags:

Your Tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

vivekamar(6106) -

dpeterson(4397) -

Noldorin(829)

Comments:

posted by dpeterson(4397) 6 months, 3 days ago 0

I have a love/hate relationship with ORMs. They can save time and make programming easier, but they come with a performance penalty. Sometimes, as mentioned in the article, they come with their own quirks that cause major performance problems when used a certain way (they mentioned building a listbox was causing thousands of select statements to run).

Now, I don't think you can lump *all* ORM's into that camp, some are very intelligent about when they retrieve data and how much they retrieve, but some aren't. I don't think you can say whether using an ORM is good or bad, it's all dependent on the situation.

I am a proponent of SQL, I think it's the best tool for the job, but sometimes, for some projects, it's not feasible to write all the SQL by hand, which makes ORMs handy. I think that working with individual objects (with simple enough data models), is negligibly slower than using SQL in things like desktop applications. However, when you get into applications under heavy load such as high-traffic web applications, the convenience of not writing some SQL is quickly outweighed by the performance effects. Though some ORMs implement pretty advanced caching strategies, so that's something else you'd have to roll on your own to help with performance.

The problem comes down to the features of ORMs being useful, and at some point even if you dont' use an ORM, you're probably going to try to add some of the same features to your codebase. Pretty soon your data access layer is just as cumbersome and just as "slow". The trick is finding the right balance of features to raw performance, and tailoring your code to the project at hand.

posted by Noldorin(829) replied to dpeterson(4397), 6 months, 1 day ago 0

For me, the dislike of ORMs is a bit simpler. I just consider them a bit of a kludge... it's like saying, let's all use relational DBs... oh wait, what we actually want is an OO DB. Yeah, too much confusion around them. OO graph DBs for the win. :-)

Most Active Users

What's this?