Eviction and expiration details
A few notes on eviction and expiration:  Expiration is a top-level construct, represented in the configuration as well as in the cache API. More on this later. While eviction is local to each cache instance, expiration is cluster-wide. Expiration lifespans and maxIdle values are replicated along with the cache entry. Expiration lifespans and maaxIdle are also persisted in CacheStores, so this information survives eviction/passivation. Only three eviction strategies are shipped, EvictionStrategy.NONE, EvictionStrategy.LRU and EvictionStrategy.FIFO, as these are deemed the most useful. If there are sufficient requests for more strategies these may be added later. As of Infinispan 4.1, EvictionStrategy.UNORDERED is also available. Architecturally, this is all-new from ground-up.