Last post Apr 04, 2016 03:15 PM by mikesdotnetting
Apr 04, 2016 02:42 PM|J@ret|LINK
My question is conceptual.
If we imagine that we have an asp.net MVC application which has to process many transactions at the same time (for example 1000 users tried to write to the same table at the same time to the SQL Server database).
Should I use EF or not? What should I use? When EF is suitable and when not? Which is the best way to do that?
Apr 04, 2016 03:15 PM|Mikesdotnetting|LINK
Conceptually, you should use Entity Framework (or any other full-featured ORM) when you want to work with data as strongly typed objects in an Object Oriented way and don't want to spend a lot of time building your own data access and repository layer.
Practically, there is a performance penalty to pay with any ORM, which may or may not be significant. If your concerns are about EF's performance under the kind of load you describe, you should stress test a sample application in the kind of environment
you expect to host it. That's the only way to answer your own question.