Geek asks and answers

MVC 3 using stored procedure vs Entity Framework 4

We are launching an MVC 3 project with Razor, and I am confused what approach should be taken when it comes to accessing / updating data. I know that we have the following options.

* Plain old ADO.NET
* LINQ to SQL
* NHibernate
* Entity Framework

But I'm more likely to use Plain Old ADO.Net (since I think it is the fastest) I would still use the Model classes, but as soon as I get the data from the class, I would like to continue and call the stored procedure using Plain Ado.Net, and not use the EF Update methods.

I would like to get your opinion if there are any drawbacks to this approach compared to using EF.

(This will be a public site with lots of traffic!)

+3
source share
3 answers

. ADO.NET. , , ORM . ORM, / , , .

, - , ORM, Hibernate ( NHibernate), , , SQL ( ..). , ORM RAD, , . , , , ADO . , , .

, , ORM , ADO, , , ADO . , !

+4

NHibernate , , , , - .

EF, "plain ado.net", , .

, ;

", , EF- , Plain Old Ado.net "

EF , , / , . EF ORM , , - .., , ado.

+1

- 60 ( 1 24 ), Entity Framework LINQ.

EF... , , Amazon S3 ( Amazon.NET SDK), .

EF caches calls, so when extracting the same object, EF is smart enough not to call the database again and return the cached object, everything was done very well, and I must say that I was restrained against EF when I started the project, but in the end it was WIN !

0
source

More articles:


All Articles