ORM Market Analysis

Question

I would like your experience with popular ORM tools to appear, for example, NHibernate, LLBLGen, EF, S2Q, Genom-e, LightSpeed, DataObjects.NET, OpenAccess, ...

From my experience: - Genom-e is silent, capable of Linq and performance, dev support - EF lacks some key features such as lazy loading, Poco support, pers.ignorance ... but in 4.o it may overcame .. - DataObjects.Net is still good, I found some errors - A steep NHibernate learning curve, 100% Linq support (like in Genom-e and DataObjects.Net), but very supportive, expandable and mature

Answer 1

http://www.ormbattle.net/

This is the best comparison you can find at the moment.

From my experience, by the way: Stay AWAY from the current version of NHibernate, if you have an interest in LINQ - use the development branch. LINQ mvoes support in the core DLL And - more importantly - much better and more complete than the limited addition of methods in current releases.

Answer 2

• ORM Meter
• Should I ever use Entity Framework 4.0?
• NHibernate - Good, Bad and Ugly what it gets!

_{(source: ormeter.net )}

Answer 3

We conducted an in-depth analysis two years ago (2010) between NHibernate, EF and Llblgen and chose the latter. We definitely think we made the right decision.

Llblgen Pro is a great and mature ORM (Entity FW has yet to be developed: direct m: n, enum, inheritance ...). Ease of using both the model and the database, first without XML, to see, just a good graphic designer.

• Highly efficient: get only the columns you need ... or use TypedList to make extensive use of merged / grouped columns ... or map your views using TypedViews or map your Store Store procedures ... or use ad-hoc requests. You can even create some templates matching your own POCO (TypeValue) and directly calling SQL !!! (we didn't have to get this far)
• From the designer, use your own infrastructure or NHibernate or Entity Framework or LINQ to SQL
• There are a lot of functionalities that you would miss as soon as you decided to go into production (prefetching, transactions, data binding helpers, paging, serialization, tuning (properties, dependency injection, authorization, audit, ...)

... but much more: a great model designer and template system.

From ORM on:

• A good use of custom templates (e.g. ASP.Net, MVC, REST or WCF) is provided by the forest system / general architecture -> allows less experienced code users to intercept and be more productive. Common solutions are reused (its costs go down: it's not “code versus understanding and integration, but code versus. Plug"). Although these are old-fashioned ASP.Net web forms, look at http: //northwind.angte- demo.com/ for what you can get with templates.
• Code for your specific application in VS, as usual. If the code is reusable, it adds code to the template (usually this means a change in an ASP-like file such as "Product" from "<% = Entity.Name%>" rather than hard staff).