Resin has supported caching, session replication (another form of caching), and http proxy caching in cluster environments for over ten years. When you use Resin caching, you are using the same platform that has the speed and scalability of custom services written in C like NginX with the usability of Java, and the industry platform Java EE. JCache JSR 107 is a distributed cache that has a similar interface to the HashMap that you know and love. To be more specific, the Cache object in JCache looks like a java.util.ConncurrentHashMap. In addition, JCache JSR 107 defines integration with CDI (as well as Spring and Guice). You can decorate services with interceptors that apply caching to the services just by defining annotations.
Resin 4 has support for JCache, and JCache support is required for Java EE 7.
Let's look at a small example to see how easy is to get started with JCache.
The above works out fairly well, but what if we want to periodically change the helloMessage. Let's say we get 2,000 requests a second, but every 10 seconds or so we would like to regenerate the helloMessage.
The message might be:
Later we would want it to change.
If we wanted it to change every 10 seconds after it was last accessed, we would do this:
For this example, we want to change it every 10 seconds after is was last modified. We would set up the timeout on the creation as follows:
This would go right in the cache method we defined earlier.
Resin's JCache implementation is built on top Resin distributed cache architecture. You get replication, and data redundancy built in.