Java Reference
In-Depth Information
you would like with JPA annotations, however without an
implementation nothing will happen. Think of JPA as the
guidelines that must be followed or an interface, while
Hibernate's JPA implementation is code that meets the API as
defined by the JPA specification and provides the under the
hood functionality.
When you use Hibernate with JPA you are actually using the
Hibernate JPA implementation. The benefit of this is that you
can swap out Hibernate's implementation of JPA for another
implementation of the JPA specification. When you use
Hibernate you are locking into the implementation because
other ORMs may use different methods/configurations and
annotations, therefore you cannot just switch over to another
ORM. As an architect you have a choice of JPA
implementations for e.g Oracle provides its JPA reference
implementation which is EclipseLink
JPA Pros:
• Isolate application from the database.
• Increase manageability of application.
• Improve developer productivity.
•
Ease
of
development
generated
correct
and
efficient
persistence logic.
• Can outperform hand-crafted SQL, reducing the number of
database round-trips.
