Managing Expiring Keys in Java Maps
As a Java developer, handling key expiry mechanisms can often be a cumbersome task. Many seek a straightforward solution that eliminates the need for manual purging and relies solely on a code-based implementation. To alleviate this challenge, it's worth delving into the Google Collections library (now Guava).
Introducing MapMaker and CacheBuilder
Guava offers two powerful tools for managing time-based maps: MapMaker and CacheBuilder. MapMaker allows for flexible customization of maps, including the ability to set expiration times for its entries. CacheBuilder, introduced in Guava 10.0, provides a modernized interface for configuring caching mechanisms.
Setting Expiration Periods
To configure expiration periods for map entries, you can use the following methods:
Example Implementation using MapMaker
ConcurrentMap<Key, Graph> graphs = new MapMaker() .concurrencyLevel(4) .softKeys() .weakValues() .maximumSize(10000) .expiration(10, TimeUnit.MINUTES) .makeComputingMap( new Function<Key, Graph>() { public Graph apply(Key key) { return createExpensiveGraph(key); } });
Enhancements in Guava 10.0
In Guava 10.0, the original MapMaker methods have been deprecated in favor of CacheBuilder. The following example demonstrates the usage of CacheBuilder:
LoadingCache<Key, Graph> graphs = CacheBuilder.newBuilder() .maximumSize(10000) .expireAfterWrite(10, TimeUnit.MINUTES) .build( new CacheLoader<Key, Graph>() { public Graph load(Key key) throws AnyException { return createExpensiveGraph(key); } });
By leveraging these tools, you can effortlessly manage time-based maps in Java, ensuring automatic purging of expired keys and optimizing the efficiency of your data handling mechanisms.
The above is the detailed content of How Can Guava's MapMaker and CacheBuilder Simplify Expiring Key Management in Java Maps?. For more information, please follow other related articles on the PHP Chinese website!