When the application updates X in the cache, X is added to the write-behind queue (if it is not there otherwise, it is replaced), and after the specified write-behind delay Coherence calls the CacheStore to update the underlying data source with the latest state of X. For Write-Behind caching, Coherence maintains a write-behind queue of the data that must be updated in the data source. Note that this only applies to cache inserts and updates - cache entries are removed synchronously from the data source. In the Write-Behind scenario, modified cache entries are asynchronously written to the data source after a configured delay, whether after 10 seconds, 20 minutes, a day, a week or even longer.
You can implement a controllable cache store that allows an application to control when it writes updated values to the data store.Ĭonsider best practices when creating a cache store implementation. Sample Controllable Cache Store Implementation.To plug in a cache store implementation, specify the implementation class name within a distributed-scheme, backing-map-scheme, cachestore-scheme, or read-write-backing-map-scheme.īefore creating a cache store implementation, review a very basic sample implementation of the .CacheStore interface. Plugging in a Cache Store Implementation.Coherence supports transparent read/write caching of any data source, including databases, web services, packaged applications and file systems however, databases are the most common use case.Ĭompare and contrast the different data source caching strategies that Coherence supports.Ĭoherence provides several cache store interfaces that can be used depending on how a cache uses a data source.
0 kommentar(er)
