Best arguments for/against introducing ORM technology into a companies dev process
- by james
I have started using ORM technology in the last few years. My first exposure was NHibernate. I then moved onto Linq 2 Sql, and Entity Framework.
The issue I have however is, there are some organisations where I have found strong opposition to introducing ORM tools.
They usually have a number of reasons:
they have a lot of built up SQL skills in the team, and are worried about the underlying SQL that ORM's generate.
they have DBA's who like to be able to see the SQL an app uses in order that can review it for best practice.
they are worried about performance (some people have "heard" the ORM's aren't as performant but have no real proof themselves - there may well be some truth in this! :).
So, I'm looking for the best or most convincing arguments that you have put forward FOR the use of ORM tools.
Equally, I would be interested in the against arguments too.
Note: this is NOT a discussion over which ORM I should use.