Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Lazy Loading and Caching Objects With Guava

DZone's Guide to

Lazy Loading and Caching Objects With Guava

Lazy loading and caching are powerful performance tools, but they can be implemented poorly. Here's how you can pull them off in Java using Google's Guava.

· Java Zone
Free Resource

Build vs Buy a Data Quality Solution: Which is Best for You? Gain insights on a hybrid approach. Download white paper now!

Lazy loading and caching are extremely useful tools in the developer toolbox, but like most tools, they can be often overused/abused — so use them sparingly. Lazy loading can be useful when creating a singleton with any variety of double-checked locking, static holder classes, enum singleton patterns, etc. Lazy loading is also great for expensive operations that you only need to handle some of the time. Hibernate heavily utilizes lazy loading. Lazy loading can either be request scoped or in a more global scope. Google's Guava provides an extremely convenient way to create lazy loaded values as well as caching individual values with or without an expiration.

Supplier

We will be using a very simple "hello world" Supplier that will log every time it is called.

public static String helloWorldSupplier() {
    log.info("supplying");
    return "hello world";
}

 View on GitHub

Suppliers.memoize

Suppliers.memoize is a simple method that takes a Supplier and returns a new Supplier that caches the value returned from the supplied Supplier.get() method. This convenient helper allows us to turn any Supplier into a lazily loaded cached value. The returned Supplier is thread-safe, backed with double checked locking and volatile fields. It even allows the original Supplier to be garbage collected once it has been called. If you are utilizing this pattern for code that is not multi-threaded, it might be useful to make a non thread-safe version.

log.info("Memoized");
Supplier memoized = Suppliers.memoize(SuppliersExamples::helloWorldSupplier);
log.info(memoized.get());
log.info(memoized.get());

 View on GitHub


2017-09-06 08:50:58.069 [main] INFO  c.s.e.common.SuppliersExamples - Memoized
2017-09-06 08:50:58.156 [main] INFO  c.s.e.common.SuppliersExamples - supplying
2017-09-06 08:50:58.157 [main] INFO  c.s.e.common.SuppliersExamples - hello world
2017-09-06 08:50:58.157 [main] INFO  c.s.e.common.SuppliersExamples - hello world


Suppliers.memoizeWithExpiration

Suppliers.memoizeWithExpiration is also straightforward. It allows us to memoize a value from a given Supplier but have it update any time we exceed the expiration time. This is a great caching mechanism for any data you know changes infrequently. A minor drawback is if the operation is expensive, you may see a hiccup every time the object needs to be reloaded. Oftentimes, though, this is not a major concern. If it is an issue, you can investigate refreshing the object asynchronously with a background thread. 

Suppliers.memoizeWithExpiration is used to cache the scraped results for our HTML/CSS Themes page and can be seen in Web scraping in Java with jsoup and OkHttp.

log.info("Memoized with Expiration");
Supplier memoizedExpiring = Suppliers.memoizeWithExpiration(
    SuppliersExamples::helloWorldSupplier, 50, TimeUnit.MILLISECONDS);
log.info(memoizedExpiring.get());
log.info(memoizedExpiring.get());
log.info("sleeping");
TimeUnit.MILLISECONDS.sleep(100);
log.info(memoizedExpiring.get());
log.info(memoizedExpiring.get());
log.info("sleeping");
TimeUnit.MILLISECONDS.sleep(100);
log.info(memoizedExpiring.get());
log.info(memoizedExpiring.get());

 View on GitHub


2017-09-06 08:50:58.157 [main] INFO  c.s.e.common.SuppliersExamples - Memoized with Expiration
2017-09-06 08:50:58.171 [main] INFO  c.s.e.common.SuppliersExamples - supplying
2017-09-06 08:50:58.171 [main] INFO  c.s.e.common.SuppliersExamples - hello world
2017-09-06 08:50:58.171 [main] INFO  c.s.e.common.SuppliersExamples - hello world
2017-09-06 08:50:58.171 [main] INFO  c.s.e.common.SuppliersExamples - sleeping
2017-09-06 08:50:58.272 [main] INFO  c.s.e.common.SuppliersExamples - supplying
2017-09-06 08:50:58.272 [main] INFO  c.s.e.common.SuppliersExamples - hello world
2017-09-06 08:50:58.272 [main] INFO  c.s.e.common.SuppliersExamples - hello world
2017-09-06 08:50:58.272 [main] INFO  c.s.e.common.SuppliersExamples - sleeping
2017-09-06 08:50:58.377 [main] INFO  c.s.e.common.SuppliersExamples - supplying
2017-09-06 08:50:58.377 [main] INFO  c.s.e.common.SuppliersExamples - hello world
2017-09-06 08:50:58.377 [main] INFO  c.s.e.common.SuppliersExamples - hello world

Build vs Buy a Data Quality Solution: Which is Best for You? Maintaining high quality data is essential for operational efficiency, meaningful analytics and good long-term customer relationships. But, when dealing with multiple sources of data, data quality becomes complex, so you need to know when you should build a custom data quality tools effort over canned solutions. Download our whitepaper for more insights into a hybrid approach.

Topics:
java ,caching ,google guava ,lazy loading ,tutorial

Published at DZone with permission of Bill O'Neil. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}