Difference between ado.net and entity framework in.net?

1>ADO.NET entity is an ORM (object relational mapping) which creates a higher abstract object model over ADO.NET components. ... Entity Framework is a wrapper for ADO.NET. Thus there is nearly no difference between those two in performance (maybe entity framework is a bit slower).

2> What is the advantage and disadvantage of Entity Framework

Advantages:

One common syntax (LINQ) for all object queries whether it is database or not , Pretty fast if used as intended , easy to implement SoC , less coding required to accomplish complex tasks.

Its fast and straight forward using LINQ/FE objects For Add/Modify/Delete/Update.

Easy to map business objects (with drag & drop tables on environment). It keeps a good performance when you work with a small / middle domain model.

Disadvantages:

You have to think in a non-traditional way of handling data , not available for every database.

If there is any schema change in database FE won’t work!!! You have to update the schema in solution as well!!!

It's limited when you work with a huge domain model. -Scalability.

3>The number in a Microsoft screencast is a maximum of roughly 250 tables per EF model. That doesn't mean EF can't handle more. If the amount of the your table is smaller than 250, you can use EF whenever, if you have more than 250 tables, e.g. 1000+, I think you have to break up your 1000+ tables into several logical groups of tables, and use one EF model per such logical group (with up to 250 tables in it). If you do not want to have several model in a project, then 1000+ tables in one model is not so good.

We know that EF is called ADO.NET EF which means that EF sits on top of the ADO.NET , which tells us that it cant be faster than ADO.NET. But remember the power of LINQ which EF provides the developers. It is really powerful when comes with EF. Since EF encapsulates ADO.NET at the background it used ADO.NET only, but the question comes why EF then?? Yes if we use EF and LINQ then the maintainability and code redundancy reduces as we donot have to write the big queries anymore like SP and all.

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Mageshwaran R6y ago
Hi,
Please refer the below link, it might helps you
https://www.c-sharpcorner.com/interview-question/difference-between-adonet-and-entity-framework
Manikandan Murugesan9y ago
1>ADO.NET entity is an ORM (object relational mapping) which creates a higher abstract object model over ADO.NET components. ... Entity Framework is a wrapper for ADO.NET. Thus there is nearly no difference between those two in performance (maybe entity framework is a bit slower).

2> What is the advantage and disadvantage of Entity Framework
Advantages:

One common syntax (LINQ) for all object queries whether it is database or not , Pretty fast if used as intended , easy to implement SoC , less coding required to accomplish complex tasks.

Its fast and straight forward using LINQ/FE objects For Add/Modify/Delete/Update.

Easy to map business objects (with drag & drop tables on environment). It keeps a good performance when you work with a small / middle domain model.

Disadvantages:

You have to think in a non-traditional way of handling data , not available for every database.

If there is any schema change in database FE won’t work!!! You have to update the schema in solution as well!!!

It's limited when you work with a huge domain model. -Scalability.
3>The number in a Microsoft screencast is a maximum of roughly 250 tables per EF model. That doesn't mean EF can't handle more. If the amount of the your table is smaller than 250, you can use EF whenever, if you have more than 250 tables, e.g. 1000+, I think you have to break up your 1000+ tables into several logical groups of tables, and use one EF model per such logical group (with up to 250 tables in it). If you do not want to have several model in a project, then 1000+ tables in one model is not so good.

We know that EF is called ADO.NET EF which means that EF sits on top of the ADO.NET , which tells us that it cant be faster than ADO.NET. But remember the power of LINQ which EF provides the developers. It is really powerful when comes with EF. Since EF encapsulates ADO.NET at the background it used ADO.NET only, but the question comes why EF then?? Yes if we use EF and LINQ then the maintainability and code redundancy reduces as we donot have to write the big queries anymore like SP and all.