<p>It's the age-old question that almost all enterprise data architects have to ask themselves atsome point in time: When using the HibernateORM framework with the Java Persistence API (JPA), should data access be mitigated through theJPA2.0 EntityManager or through the underlying Hibernate Session?</p><p>EntityManager is part of the Java Persistence API (JPA) standard, and who can really argueagainst using something that is standardized? But, of course, the problem with a standard is thatit often represents the lowest common denominator with regards to what everyone in the communitycan agree upon. And who wants to use the tool that represents the lowest common denominator?</p><p>At the other end of the spectrum is the Hibernate Session, the integral part of the Hibernate ORMecosystem that provides CRUD-based interactionswith persistent entities. It is JPA compliant, so it can do everything the specification does, butit is not confined to the JPA standard, and as such, it has a vast array of interesting featuresthat might compel developers to ditch the EntityManager with a vengeance.From a team point of view, we wish we had only one API. We arereally trying to push into the standard as much as we can.</p><p>Emmanuel Bernard, Data Architect. Hibernate</p><p><a href="http://www.theserverside.com/news/2240186700/The-JPA-20-EntityManager-vs-the-Hibernate-Session-Which-one-to-use">Keep reading...</a></p>