This project is read-only.

Move off of EF (Dapper or nHibernate)


Please move off of EF. It's not fit for high traffic sites and sucks period.
  1. nHibernate?
  2. Really fast but not very convenient for developers -
P.S. Everything will be fine when EF start supporting 2-level caching


ShujaatKagathra wrote Sep 25, 2014 at 6:49 PM

Stackoverflow, one the most high traffic, database driven website uses
and we all know about hi performance of stackover flow. more details for

riadhgomri wrote Jul 8, 2015 at 1:47 PM

Why are you saying Really fast but not very convenient for developers - ?
Not convenient for who ? it is really fast and really elegant

shurub3l wrote Nov 10, 2015 at 8:27 AM

Go for! :)

samdubey wrote Jun 28, 2016 at 11:57 AM

+1 for Dapper.Net

praveennerd wrote Jul 8, 2016 at 4:19 PM

Please ... Please ... Please.

Move to dapper. And give choice to move to DB servers like MySQL, MongoDB etc.. I love MS Sql Server but for start ups it's too much. It's next to impossible to get cheap and good MS SQL server hosting plans.

babakjahangiri wrote Feb 21 at 12:48 AM

I Vote for Dapper

MVC has enough Caching , SQL also has Caching system

I believe EF Caching is useless for NopCommerce and reduce the performance