CHAPTER 13 Optimizing fetching and caching persistent instances.
CHAPTER 13 Optimizing fetching and caching persistent instances. A cache concurrency strategy defines the transaction isolation details for a particular item of data, whereas the cache provider represents the physical cache implementation. Use of the second-level cache is optional and can be configured on a per-class and per-collection basis each such cache utilizes its own physical cache region. Hibernate also implements a cache for query resultsets that integrates closely with the second-level cache. This is an optional feature; it requires two additional physical cache regions that hold the cached query results and the timestamps when a table was last updated. We discuss the query cache in the next chapters because its usage is closely tied to the query being executed. We ve already discussed the first-level cache, the persistence context, in detail. Let s go straight to the optional second-level cache The Hibernate second-level cache The Hibernate second-level cache has process or cluster scope: All persistence contexts that have been started from a particular SessionFactory (or are associ- Figure 13.7 Hibernate s two-level cache architecture
Searching for affordable and proven webhost to host and run your servlet applications? Go to Linux Web Hosting services and you will find it.