ADO.Net or ORMs?

There is nothing wrong with using ADO.NET. It’s what drives all the ORM solutions in .NET. The current attitude is using raw ADO.Net is a bad thing. If it gets the job done, then what’s the issue?

Yet it seems .NET developers are running in droves to jump on the ORM bandwagon. ORMs are just one of many tools in the data access toolbox.

In the early 2000’s ORMs took the Java world by storm. Store procedures were shunned. It was ORM or nothing. A half decade later Java developers realized that the best solution uses both an ORM and stored procedures, each has strengths.

Use the best tool for the job. ORMs can automate much of the CRUD from the application. Stored procedures are good for adding abstraction, adding a layer of security and optimizing area’s that need to be highly performant.

Choose the best tool for the job.