Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What are the major differences between Data Access Application Block, NHibernate, ADO.NET Entity Framework and LINQ to SQL with respect to performance, business logic, scalability and flexibility?
What you are asking is a pretty large question. Here’s a similar question and my answer to that question can give you a lot of good reading to do on the various .NET ORMs:
NHibernate, Entity Framework, active records or linq2sql
You won’t notice a ton of difference in performance between the various options in the large majority of scenarios. All of the options are built on ADO.NET and allow you do use raw ADO.NET to get the best possible performance.
All solutions are flexible to the extent you are willing to write your own code. NHibernate provides the most features out of the box, by far.
Scalability is difficult to answer, there are ways to achieve scale with all of the options, but some make it easier than others. Again, NHibernate is the most feature rich from a scalability standpoint out of the box, providing features like both a level 1 and level 2 cache.
For business logic, the three ORMs will work approximately the same, but the Data Access Application Block is not an ORM and doesn’t provide any of the features of an ORM, so you are completely on your own mapping your relational table data into objects from Data Readers or DataSets.