A few years ago, a very clever guy wrote a blog about IBM BPM Caching Using WebSphere DynaCache (http://blog.edwardborner.com/2014/07/ibm-bpm-caching-using-websphere.html). I’ve always assumed that this blog entry was the seed that grew into the caching properties of Ajax Services in IBM BPM.

In more recent versions (2017.06+) of IBM BPM this capability has been expanded to both General System Services and Integration Services. In my view, this feature is under-rated and under-used (or at least ineffectively used) in the majority of IBM BPM implementations.

It is a real quick win; spend a little time thinking about the data in your Services, tick a few boxes and enter some numbers and you're done. You’ve just saved every user a second or two every time they run a Task or halved the number of integration calls to lookup some metadata.

Review every Service in your process application and make a conscious decision about caching. Hopefully your artefact naming convention makes it easy to pick the best candidates. Use @tags (and Smart Folders) to track Services with caching enabled.