§The Play cache API
Caching data is a typical optimization in modern applications, and so Play provides a global cache. An important point about the cache is that it behaves just like a cache should: the data you just stored may just go missing.
For any data stored in the cache, a regeneration strategy needs to be put in place in case the data goes missing. This philosophy is one of the fundamentals behind Play, and is different from Java EE, where the session is expected to retain values throughout its lifetime.
The default implementation of the cache API uses Ehcache.
§Importing the Cache API
Play provides both an API and an default Ehcache implementation of that API. To get the full Ehcache implementation, add ehcache to your dependencies list:
libraryDependencies ++= Seq(
ehcache
)This will also automatically set up the bindings for runtime DI so the components are injectable.
To add only the API, add cacheApi to your dependencies list.
libraryDependencies ++= Seq(
cacheApi
)The API dependency is useful if you’d like to define your own bindings for the Cached helper and AsyncCacheApi, etc., without having to depend on Ehcache. If you’re writing a custom cache module you should use this.
§JCache Support
Ehcache implements the JSR 107 specification, also known as JCache, but Play does not bind javax.caching.CacheManager by default. To bind javax.caching.CacheManager to the default provider, add the following to your dependencies list:
libraryDependencies += jcacheIf you are using Guice, you can add the following for Java annotations:
libraryDependencies += "org.jsr107.ri" % "cache-annotations-ri-guice" % "1.0.0"§Accessing the Cache API
The cache API is defined by the AsyncCacheApi and SyncCacheApi interfaces, depending on whether you want an asynchronous or synchronous implementation, and can be injected into your component like any other dependency. For example:
import play.cache.*;
import play.mvc.*;
import javax.inject.Inject;
public class Application extends Controller {
private AsyncCacheApi cache;
@Inject
public Application(AsyncCacheApi cache) {
this.cache = cache;
}
// ...
}Note: The API is intentionally minimal to allow various implementations to be plugged in. If you need a more specific API, use the one provided by your Cache library.
Using this simple API you can store data in the cache:
CompletionStage<Done> result = cache.set("item.key", frontPageNews);Optionally you can specify an expiration (in seconds) for the cache:
}
{
// Cache for 15 minutes
CompletionStage<Done> result = cache.set("item.key", frontPageNews, 60 * 15);You can retrieve the data later:
CompletionStage<News> news = cache.get("item.key");You can also supply a Callable that generates stores the value if no value is found in the cache:
CompletionStage<News> maybeCached = cache.getOrElseUpdate("item.key", this::lookUpFrontPageNews);To remove an item from the cache use the remove method:
CompletionStage<Done> result = cache.remove("item.key");To remove all items from the cache use the removeAll method:
CompletionStage<Done> resultAll = cache.removeAll();removeAll() is only available on AsyncCacheApi, since removing all elements of the cache is rarely something you want to do sychronously. The expectation is that removing all items from the cache should only be needed as an admin operation in special cases, not part of the normal operation of your app.
Note that the SyncCacheApi has the same API, except it returns the values directly instead of using futures.
§Accessing different caches
It is possible to access different caches. In the default Ehcache implementation, the default cache is called play, and can be configured by creating a file called ehcache.xml. Additional caches may be configured with different configurations, or even implementations.
If you want to access multiple different ehcache caches, then you’ll need to tell Play to bind them in application.conf, like so:
play.cache.bindCaches = ["db-cache", "user-cache", "session-cache"]
By default, Play will try to create these caches for you. If you would like to define them yourself in ehcache.xml, you can set:
play.cache.createBoundCaches = false
Now to access these different caches, when you inject them, use the NamedCache qualifier on your dependency, for example:
import play.cache.*;
import play.mvc.*;
import javax.inject.Inject;
public class Application extends Controller {
@Inject @NamedCache("session-cache") SyncCacheApi cache;
// ...
}§Setting the execution context
By default, all Ehcache operations are blocking, and async implementations will block threads in the default execution context.
Usually this is okay if you are using Play’s default configuration, which only stores elements in memory since reads should be relatively fast.
However, depending on how EhCache was configured and where the data is stored, this blocking I/O might be too costly.
For such a case you can configure a different Akka dispatcher and set it via play.cache.dispatcher so the EhCache plugin makes use of it:
play.cache.dispatcher = "contexts.blockingCacheDispatcher"
contexts {
blockingCacheDispatcher {
fork-join-executor {
parallelism-factor = 3.0
}
}
}
§Caching HTTP responses
You can easily create a smart cached action using standard Action composition.
Tip: Play HTTP
Resultinstances are safe to cache and reuse later.
Play provides a default built-in helper for the standard case:
@Cached(key = "homePage")
public Result index() {
return ok("Hello world");
}§Custom implementations
It is possible to provide a custom implementation of the cache API that either replaces or sits alongside the default implementation.
To replace the default implementation based on something other than Ehcache, you only need the cacheApi dependency rather than the ehcache dependency in your build.sbt. If you still need access to the Ehcache implementation classes, you can use ehcache and disable the module from automatically binding it in application.conf:
play.modules.disabled += "play.api.cache.ehcache.EhCacheModule"
You can then implement AsyncCacheApi and bind it in the DI container. You can also bind SyncCacheApi to DefaultSyncCacheApi, which simply wraps the async implementation.
Note that the removeAll method may not be supported by your cache implementation, either because it is not possible or because it would be unnecessarily inefficient. If that is the case, you can throw an UnsupportedOperationException in the removeAll method.
To provide an implementation of the cache API in addition to the default implementation, you can either create a custom qualifier, or reuse the NamedCache qualifier to bind the implementation.