Skip to main content

Simple is beautiful: Guava LoadingCache

Cache is king.

Database lookups can be expensive and RAM prices have been falling for years to the point that developers don't care anymore (ops do, btw).
So what if you could use those gigabytes of RAM for caching expensive queries or frequently used data? If you are a Java developer chances are that you came across Ehcache, Spring cache, or perhaps rolled your own.
Disclaimer: not the Guava stuff described in this post

Grails bundles Ehcache because it can be used by Hibernate and also has a plugin which allows to cache methods just by annotating them. Unfortunately Ehcache has some quirks and with the stock configuration it will also not allow parallel deployment (I documented a fix here on this blog).

An alternative cache implementation that I recently had a chance to use is the Guava LoadingCache. The implementation is so elegant that it will make you want to use it everywhere! Basically you build a cache, configure TTL and size (optional) and supply a loader callback that will be invoked whenever an entry cannot be found in the cache. Example here.

Assuming you are accessing the cache implementation directly, no more complex if-peek-then-return-else-load-put-return. From now on just:

cache.getEntry(k)

An additional benefit is that Guava does not carry dependencies, is OSGi-ready, and will keep your project lighter.

Comments

Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

RUNDECK job maintenance

Learn more about Rundeck.

Now that I have a fair number of jobs scheduled by Rundeck, how do I periodically prune the job execution history and keep only the last, say, 30 executions for each job?