Originally posted by Mark Spritzler:
Personally, the more transactional and changing the data is, the less I would cache it at all. Because pretty soon, all your resources are going to updating all the servers with the latest data, and no processing power to support your clients, so the drag and slowness becomes more than going to the database to get your data.
Data that remains the same is the highest roi on loading data into a distributed cache.
Originally posted by James Sutherland:
TopLink (and EclipseLink) provide several features for handling stale cached data. Which feature you choose depends on have often your data is updated and what your applications level of tolerance for stale data is.