Why use JPA or ORM?

Java Persistence Persistence Products

EclipseLink

There are many persistence products to choose from. Most persistence products now support a JPA interface, although there still are some exceptions. Which product you use depends on your preference, but most people would recommend you use the JPA standard whichever product you choose. This gives you the flexibility to switch persistence providers, or port your application to another server platform which may use a different persistence provider.

Determining which persistence product to use involves many criteria. Valid things to consider include:

• Which persistence product does your server platform support and integrate with?
• What is the cost of the product, is it free and open source, can you purchase enterprise level support and services?
• Do you have an existing relationship with the company producing the product?
• Is the product active and does it have a large user base?
• How does the product perform and scale?
• Does the product integrate with your database platform?
• Does the product have active and open forums, do questions receive useful responses?
• Is the product JPA compliant, what functionality does the product offer beyond the JPA specification?

Existing Persistence Products

The following table summarises existing persistence products.^[1]

1. ↑ Last updated 2016-07-05
2. ↑ Application server that includes the product as their JPA implementation