Efforts to design, implement and maintain CRUD

Question

What percentage of your overall development efforts are you spending on implementing and supporting simple create, read, update, and delete (CRUD) methods at your data access level?

Does switching to ORM, like Hibernate or Entity Framework, result in significant savings? Are there any designer smells that tell you about switching to ORM for your data access level - is that a good choice?

Regards, Ashish

Answer 1

Having recently spent an absurd amount of hours (perhaps around 40%), duplicating what ORM would do in minutes, I have to say that whenever you can let well-tested frameworks generate (and support!) Basic CRUD operations, GET IT!

Let the structure do what it transcends. Spend time with an application that truly adds value, the business problem you are solving. Only when the structure falls, if you really decide to get around it. “Falling short” may include performance, but overall there are “hooks and handles” in the “framework” to do what you need to do.

/: "StoredProcedureWrapper" 40- DAO, / ORM

Ruby/Rails Groovy/Grails ORM, .

Spring/Hibernate , .

10 , ORM, "" JDBC , ORM .