Why not NHibernate?

Posts   
 
    
jimph
User
Posts: 63
Joined: 06-Jun-2013
# Posted on: 07-Aug-2013 20:59:25   

I am trying to choose a framework for our project. The question why we are not using NHibernate will certainly arise from many as it is known to many. Similarly, keeping aside the solid designer, what does LLBLGen framework has that cannot be achieved by NHibernate (for me LLBLGen various options for customize/optimize access layer is superior, for large scale development).

If you are familiar with both would you kindly give me your input using your experience (and this includes LLBLGen engineers pleasesimple_smile

Many thanks, jp

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 08-Aug-2013 07:30:46   

Hi jp,

This thread could be helpful: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=14457 We don't make ORM comparisons as we believe that the developer has to answer the question "What do I need", then evaluate the O/RM frameworks and decide which one to use. That's why LLBLGen Designer supports all relevant frameworks. If you want to change the O/RM framework later you can switch them in the Designer and preserve your model intact.

So, for me there is not an easy answer, I hope you get more feedback from the community wink

David Elizondo | LLBLGen Support Team
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39912
Joined: 17-Aug-2003
# Posted on: 08-Aug-2013 13:30:54   

jimph wrote:

I am trying to choose a framework for our project. The question why we are not using NHibernate will certainly arise from many as it is known to many. Similarly, keeping aside the solid designer, what does LLBLGen framework has that cannot be achieved by NHibernate (for me LLBLGen various options for customize/optimize access layer is superior, for large scale development).

to name a few things:

  • The Linq provider of nhibernate is still not able to do left joins and is less mature than ours.
  • It's unlikely NHibernate will get an async api (ours is in beta for v4.0, see customer area)
  • NHibernate is very slow. See: http://pastebin.com/AdsKitr3

It has its uses and has stuff our framework doesn't (real value types, poco classes), but in practice, does one really need those?

Bugfixes are not coming very quickly in nhibernate as well, progress is rather slow. We fix bugs within a few days, tops.

But no worries, you can switch frameworks inside the designer at any time. simple_smile

Frans Bouma | Lead developer LLBLGen Pro