What is the Scheduled Write-Behind strategy?
Scheduled Write-Behind Strategy First of all, please note that this strategy is not included in version 4.0 but it will be implemented at a later stage. ISPN-328 has been created to track this feature request. If you want it implemented, please vote for it and don't forget to watch it to be notified of any changes. The following explanation refers to how we envision it to work. Â In this mode, Infinispan would periodically store changes to the underlying cache store. The periodicity could be defined in seconds, minutes, days...etc. Â Since this strategy is oriented at cache stores with high latency or expensive operation cost, it makes sense to coalesce changes, so that if there're multiple operations queued on the same key, only the latest value is applied to cache store. With this strategy,the window of inconsistency between the contents of the cache and the cache store depends on the delay or periodicity configured. The higher the periodicity, the higher the chance of inconsistency