Skip to main content
Jump to: navigation, search

Difference between revisions of "EclipseLink/UserGuide/JPA/Basic JPA Development/Caching/Caching Overview"

Line 9: Line 9:
*[[EclipseLink/Examples/JPA/Caching|How to use caching]]
*[[EclipseLink/Examples/JPA/Caching|How to use caching]]
*[[EclipseLink/Examples/JPA/CacheCoordination|How to enable cache coordination]]
*[[EclipseLink/Examples/JPA/CacheCoordination|How to enable cache coordination]]
*[[EclipseLink/Examples/JPA/DCN|How to use database event driven cache invalidation using Oracle DCN/QCN]]}}
*[[EclipseLink/Examples/JPA/DCN|How to use database event driven cache invalidation]]}}
=Caching Overview=
=Caching Overview=

Revision as of 15:25, 3 May 2012

Caching Overview

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 accessing them in-memory to minimize database access.
  • Manage locking and isolation level.
  • Manage object identity.

For more information about the EclipseLink cache and its default behavior, see Introduction to Cache.

EclipseLink defines the following entity caching annotations:

  • @Cache
  • @TimeOfDay
  • @ExistenceChecking

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.

For more information, see the following:

Version: 2.2.0 DRAFT
Other versions...

Back to the top