Have ORMs introduced extra complexity into our codebase?

home
architecture
view story

4 Kicks

Kick It

Drop Kick

Kicked

Have ORMs introduced extra complexity into our codebase?(paulstack.co.uk)

submitted by stack72(35) 9 months, 7 days ago

Thinktank article to make us think about whether ORMs are a good thing or a bad thing for our codebases

2 comments |category: Architecture |Views: 71
Tweet

tags: Architecture 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:

Comments:

posted by vijayst(1311) 9 months, 6 days ago 0

ORM is definitely a good thing when used appropriately. It becomes bad when developers do not understand the ORM framework. Or the garbage collection framework. However, I have recently read articles doing a comparision between different ORM framework performance. The performance of EF fared relatively lower than its peers like NHibernate or Spring.Net.

Having said that, I really love the simplicity of a lean DAL via SqlHelper classes. Using SqlHelpers with stored procedures allow developers to understand the SQL queries better and what goes on SQL server like execution plans.

posted by dpeterson(4393) 9 months, 3 days ago 0

One of the comments on the article hit the nail on the head: People shouldn't use ORMs because they don't want to write SQL, they should use ORMs so that they can populate their business objects in their code.

Most Active Users

What's this?