Caching fundamentals Choosing a cache provider For now, (Adelphia web hosting)
Caching fundamentals Choosing a cache provider For now, Hibernate forces you to choose a single cache provider for the whole application. Providers for the following open source products are built into Hibernate: EHCache is a cache provider intended for a simple process scope cache in a single JVM. It can cache in memory or on disk, and it supports the optional Hibernate query result cache. (The latest version of EHCache now supports clustered caching, but we haven t tested this yet.) OpenSymphony OSCache is a service that supports caching to memory and disk in a single JVM, with a rich set of expiration policies and query cache support. SwarmCache is a cluster cache based on JGroups. It uses clustered invalidation but doesn t support the Hibernate query cache. JBoss Cache is a fully transactional replicated clustered cache also based on the JGroups multicast library. It supports replication or invalidation, synchronous or asynchronous communication, and optimistic and pessimistic locking. The Hibernate query cache is supported, assuming that clocks are synchronized in the cluster. It s easy to write an adaptor for other products by implementing org.hibernate. cache.CacheProvider. Many commercial caching systems are pluggable into Hibernate with this interface. Not every cache provider is compatible with every concurrency strategy! The compatibility matrix in table 13.1 will help you choose an appropriate combination. Setting up caching involves two steps: First, you look at the mapping metadata for your persistent classes and collections and decide which cache concurrency Table 13.1 Cache concurrency strategy support Concurrency strategy cache provider Read-only Nonstrictread- write Read-write Transactional EHCache X X X OSCache X X X SwarmCache X X JBoss Cache X X
We would like to recommend you tested and proved virtual web hosting services, which you will surely find to be of great quality.