c# - Choice of OR Mapper for a new project -


We are going to start a new project, it will be a group of web applications with a good number of shared components. There will be 50,000 unique user visits per day and it will be some kind of management panel. All the projects are being constructed in ASP.N.M. 2 will be in MV2 and they all will work on a SQL Server database.

We have been in NHibernate for a long time until I do not get the website, where performance testing for NHibernate looks very bad compared to other mappers. In this summary I got the library unknown earlier, really promising Looks, but both are - advantages and disadvantages.

BLToolkit is a support for weaker communities, very few examples and I have not really heard of any person who uses it in a big project. Apart from this, it is very light, which means it does not support many relationships, lazy loading and caching ...

The performance on the other hand is really good, and Linq's very good support is also. / P>

In this case I am between choosing one of those methods:

  1. Do not care too much about performance and use Nhibernate or EF or just L2SQL (which One would be better?) And the use of ORMapper has more useful functionality.
  2. Focus on that great performance, and build some solutions on the basis of this library, which is predominantly Use as a good basis. Maybe I do not need caching if I will use action caching in MVC. Probably I do not need associations, as far as I can well write LINQ questions with expressions. Maybe I do not need lazy loading, as long as I will carefully create the exact methods that I will meet with DB.

I am not looking for the judgment of this matter. What I am asking is a little discussion, let me explain some of the problems I have not considered, or not only about using BLToolkit but also sharing some experiences with me about other or mappers.

Can you create prototypes with two different ORMs, and see if Do they perform enough for your needs? You can write some throw "display spike" code, and you can use sample data with your sample data in Visual Studio.

I think the ORM will have to choose based on the belief that the option will not perform well in a timely adaptation - as long as you have not tested to confirm your doubts.


Regarding related ormbattle.net, this is - it's one of the NHibernate developers, it's a while ago, I do not know whether ormbattle.net has changed since then.

SQL is no longer evolving from LINQ - so if you want to use an ORM from Microsoft, EF would be the best option.

I personally prefer the EF to NHibernate, but the current version of the EF executes the full LINQ implementation over the current version of NHibernate NHibernate 3 (later this year) will be full LINQ support, as well Together, another type-safe API will be called.


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -