Ehcache

Ehcache features memory and disk stores, replicate by copy and invalidate, cache loaders, cache extensions, cache exception handlers, listeners, a gzip caching servlet filter and much more ...

Ehcache is available under an Apache open source license and is actively developed, maintained and supported.

Features:

• Fast and Light Weight:
• Fast
• Simple
• Small foot print
• Minimal dependencies
• Scalable:
• Provides Memory and Disk stores for scalabilty into gigabytes
• Scalable to hundreds of caches
• Tuned for high concurrent load on large multi-cpu servers
• Multiple CacheManagers per virtual machine
• Flexible:
• Supports Object or Serializable caching
• Support cache-wide or Element-based expiry policies
• Provides LRU, LFU and FIFO cache eviction policies
• Provides Memory and Disk stores
• Distributed Caching
• Standards Based:
• Full implementation of JSR107 JCACHE API
• Extensible:
• Listeners may be plugged in
• Peer Discovery, Replicators and Listeners may be plugged in
• Cache Extensions may be plugged in
• Cache Loaders may be plugged in
• Cache Exception Handlers may be plugged in
• Application Persistence:
• Persistent disk store which stores data between VM restarts
• Flush to disk on demand
• Supports Listeners:
• CacheManager listeners
• Cache event listeners
• JMX Enabled
• Distributed:
• Support for replication via RMI or JGroups
• Peer Discovery
• Reliable Delivery
• Synchronous Or Asynchronous Replication
• Copy Or Invalidate Replication
• Transparent Replication
• Extensible
• Bootstrapping from Peers
• Cache Server:
• #RESTful cache server
• #SOAP cache server
• #comes as a WAR or as a complete server
• Java EE and Applied Caching:
• Blocking Cache to avoid duplicate processing for concurrent operations
• SelfPopulating Cache for pull through caching of expensive operations
• Java EE Gzipping Servlet Filter
• Cacheable Commands
• Works with Hibernate
• High Quality:
• High Test Coverage
• Automated Load, Limit and Performance System Tests
• Production tested
• Fully documented
• Trusted by Popular Frameworks
• Conservative Commit policy
• Full public information on the history of every bug
• Responsiveness to serious bugs
• Open Source Licensing:
• Apache 2.0 license

What is new in this release:

• Ease of use. Tuning cache sizes is now as simple as setting the maximum number of bytes. No more setting maximum entry counts and juggling eviction parameters to approximate the maximum amount of system memory your cache can use.
• Greater efficiency. Ehcache now efficiently manages caches based on their memory footprint and can dynamically balance their resource use based on runtime size information.

What is new in version 2.4.2:

• This version adds support for Terracotta 3.5.1 and includes a couple of minor bugfixes.

What is new in version 2.4.1:

• This update to Ehcache 2.4 (also referred to as Ehcache with Search) provides a few minor feature enhancements and bugfixes.

What is new in version 1.6.0:

• This release introduces a new high performance cache core, which is two orders of magnitude faster.

What is new in version 1.6.0 Beta 2:

• Allow multiple replication schemes to be used within the same CacheManager. i.e. use JMS for some caches and RMI for others.
• Add a reference to Ehcache from CacheStatistics.
• Add FINE level LOG statement for Hibernate EhCache provider puts. This enables puts to be debugged with LOG statement.
• Removed cacheManager.getCachePeerProvider() in favour of cacheManager.getCacheManagerPeerProvider("scheme") where scheme is the replication scheme. Each replicator type can then call its own scheme provider, allowing multiple replication schemes to be used within the same CacheManager.

What is new in version 1.5.0:

• Fix loading of net.sf.ehcache.hibernate.EhCacheProvider from multiple class loaders. The insistence that a leading slash be at the front of the "net.sf.ehcache.configurationResourceName" property has been removed. If this fix causes anyone an issue, add the "/" to the front of your path.
• Updated the BlockingCache.get() JavaDoc to clarify the contract when a RuntimeException is thrown.
• Added a more meaningful LOG message when a null element is encountered from a replication. The only reason that an element can be null is because a SoftRefernence has been reclaimed by the JVM. The log message recommends either increasing heap or setting -Xms to be the same as -Xmx as the Sun JDK will reclaim SoftReferences in preference to increasing heap.
• The remote debugger has had many improvements. It is now packaged in its own tarball available from the downloads page, and also continues to be published as a maven module. It is not in the core tarball so that more focus can be given to it.

Requirements:

• Java 2 Standard Edition Runtime Environment