When a Java HotRod client invalidates (remove) an entry it is possibile that this action is not propagated with enough speed to other clients due to the async nature of event notifcations used by NearCache, an so it is possibile that another client looks up a stale entry from its near cache.

A typical "writer client" scenario is:

• update the database and commit the transaction
• invalidate the entry which represents the updated (only a "remove")

The "reader" procedure is:

• lookup in the cache (nearcache, backed by the remote Infinispan cluster)
• in case of "cache miss" perform a lookup on the database and write the entry in the cache