In the simple caching mode, each VM maintains its own cache of the information. Any changes made by other servers will not be recognized in this server until the cache entry is manually or automatically invalidated. This mode is suitable for read-only repositories (which includes repositories like product catalogs where all changes are made on a staging server and not a live server) or architectures where you can guarantee that only one server will handle a particular repository item.
You can use the item-cache-timeout attribute together with simple cache mode for caching user data associated with a particular session. If only one user at a time is accessing an item type, this approach can generally prevent access to stale data from a cache without the overhead imposed by locked mode caching. See Cache Timeout in this section for more information.
You can also use simple cache mode in cases where it is practical to invalidate caches manually by calling these methods:
Class | Method |
|---|---|
|
|
|
|
|
|
See the Cache Flushing section of this chapter, which also describes the Cache Invalidator service, which can be used to control cache invalidation manually.
