Whenever a database write occurs, you then need to invalidate every
cache.  Or, as you mentioned, invalidate your local cache, the central
cache, and then have some additional application to notify all the
other local caches that something has changed.

That's along the lines of what Gavin recommended above - using
ActiveMQ to send those notification messages to all the appropriate
caches.

On Sep 11, 4:28 pm, "PlumbersStock.com" <[EMAIL PROTECTED]>
wrote:
> Wouldn't it be easiest just to employ local caches that pull from a
> central cache that pulls from your original data? That's probably what
> I'd do but I don't do anything fancy with the cache. Maybe with a
> little extra logic to cause the local cache items to expire when the
> central cache expires.

Reply via email to