Learn the pros, and cons of the Java Caching System, Guava, Caffeine, Ehcache, Infinispan, Coherence Community Edition, Ignite, Geode, and Hazelcast.
Join the DZone community and get the full member experience. Last week, we described several criteria to look at to choose a cache. This week, it’s time to list Java cache providers based on these criteria. JCS is a distributed caching system written in Java. It is intended to speed up applications by providing a means to manage cached data of various dynamic natures. Like any caching system, JCS is most useful for high read, low put applications. Latency times drop sharply and bottlenecks move away from the database in an effectively cached system. The JCS goes beyond simply caching objects in memory. It provides numerous additional features: Guava is a set of core Java libraries from Google that includes new collection types (such as multimap and multiset), immutable collections, a graph library, and utilities for concurrency, I/O, hashing, caching, primitives, strings, and more! It is widely used on most Java projects within Google, and widely used by many other companies as well. Guava is a single JAR that provides cache among many other capabilities A third-party project provides a JCache adapter The get method accepts a Callable parameter that allows to get a value from the cache or compute it and store it if it’s not found The API uses soft and weak references in keys and values Allows you to attach event handlers when entries are evicted Caffeine is a high performance, near optimal caching library.
