EclipseLink/UserGuide/JPA/Basic JPA Development/Caching/Caching Overview
|Mailing List • Forums • IRC • mattermost|
|Open • Help Wanted • Bug Day|
The EclipseLink cache is an in-memory repository that stores recently read or written objects based on class and Id values. EclipseLink uses the cache to do the following:
- Improve performance by holding recently read or written objects and their relationships and accessing them in-memory to minimize database access.
- Manage locking and isolation level.
- Manage object identity.
EclipseLink offers an integrated and functional cache including the following features:
- isolated persistence context cache (L1), and shared persistence unit cache (L2)
- caching configurable at the Entity level, entities can be cached, or not, cached entities can reference non-cached entities
- multiple cache type options (weak, soft, full, weak-cache, soft-cache)
- configurable size
- cache indexes
- in-memory querying and conforming
- time to live, and daily cache invalidation
- clustered cache coordination through RMI and JMS
- database event driven cache invalidation and Oracle DCN/QCN
- support for JPA 2.0 @Cachable configuraiton and API
- extended JpaCache API
- query cache
EclipseLink supports the following caching annotations:
EclipseLink also provides a number of persistence unit properties that you can specify to configure the EclipseLink cache (see How to Use the Persistence Unit Properties for Caching). These properties may compliment or provide an alternative to the usage of annotations.