Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/UserGuide/JPA/sandbox/caching"
< EclipseLink | UserGuide | JPA
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | . | + | =Caching= |
| + | |||
| + | The EclipseLink cache is an in-memory repository that stores recently read or written objects based on class and primary key 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. | ||
| + | |||
| + | Topics: | ||
| + | |||
| + | *[[EclipseLink/UserGuide/JPA/sandbox/caching/Cache Architecture|Cache Architecture]] | ||
| + | *[[EclipseLink/UserGuide/JPA/sandbox/caching/Cache Concepts|Cache Concepts]] | ||
| + | |||
| + | *[[EclipseLink/UserGuide/JPA/sandbox/caching/Cache Coordination|Cache Coordination]] | ||
| + | *[[EclipseLink/UserGuide/JPA/sandbox/caching/Cache API|Cache API]] | ||
Latest revision as of 17:16, 18 February 2011
Caching
The EclipseLink cache is an in-memory repository that stores recently read or written objects based on class and primary key 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.
Topics: