This document compares the Entity and NHibernate ORM frameworks. NHibernate was developed for Java in 2001 and ported to .NET frameworks, supporting all databases. It has a 2nd level cache, concurrency strategies, and rich mapping capabilities but can require more queries and be more difficult to optimize for database power. Entity was developed for C# and .NET in 2008 and has improved LINQ SQL generation, strong .NET and Microsoft integration, and easier optimization. However, it works in an attached mode to the database and is not recommended for real-time apps. Both frameworks have good community support but Entity's community is larger.

1. ENTITY AND NHIBERNATE
ORM FRAMEWORKS
COMPARED
~ Zoltan, Iszlai - Oct 22, 2015

2. Nhibernate ORM

3. INTRO
 Developed for JAVA
 Created in 2001
 Ported to .NET 1.1, 2, 3.5
 All Databases supported (Oracle)
 Good community support
 Free/Open source (LGPL license)

4. PROS AND CONS
 2nd level cache
 Concurrency strategy's
 Rich mapping capability
 Access is more abstract and portable
 More queries will need to be run
 More difficult to use the power of DB
 Smaller community (documentation?)
 Slightly slower, because on on-fly SQL generation

5. Entity ORM Framework

6. INTRO
 Developed for C#, MS technologies
 Created in 2008
 Ported to all up to date .NET versions
 Specific database support (Oracle)
 Good community support, full MS support
 Can work with domain specific objects and properties

7. PROS AND CONS
 Improved SQL generation from LINQ
 Entity is the growing trend,
with a large community
 Very good .NET integration (MS)
 Easier to optimize and faster to develop
 MetaData class creation
 Works in an attached mode to the DB
 Not recommended for real-time Apps

8. Thank you for listening