With write-behind strategy, cache agents handle writes to cache and to the backing store.
First the inference agent writes data to the cache and then the cache agent or agents write that data to the backing store.
Write Behind Options
For backing store inserts and updates, one write-behind thread is used for each entity type. Deletes are performed by the distributed cache threads (configurable) and they are synchronously deleted from the database.
Advantages
Disadvantages
Batches writes during the delay period which increases database call efficiency and minimizes network traffic.
Offloads cache and database work to the cache agent.
Does not offer database write tuning controls.
Can be slower than cache aside.
If enough cache agents fail, the cache management layer won’t be able to persist a write that was done previously, resulting in an inconsistent database.