TheServerSide.Net has just posted this great case study about an ORM. My experience is yet again confirmed by this case study:
Database administrators in particular have been notoriously difficult to convince when it comes to O/RM, if they can be convinced at all. After all, they are hardly going to want to put themselves out of a job. Besides, how could a tool ever issue as clean code as a skilled DBA with a fine, manually tuned data access layer?ORMs are darn difficult to sell to DBAs, ORMs step all over their comfort zone.
In my modest opinion, DBA's opposition is a mistake. DBAs should embrace ORMs to do their trivial work, recovering valuable (and expensive) time where DBA excel: modeling, tunning databases, rewiring ORM SQL to handcrafted stored procedures when needed and making those custom stored procedures ORM just can't do.
Ages ago some lunatics proposed that compilers should generate assembler code for developers. Developers had the same reaction: no compiler could ever generate assembler code that could match their handcrafted code. And here we are using compilers and interpreters for most of our work.
Open your mind. Embrace ORMs.
No comments:
Post a Comment