Write behind
Most users of Coherence choose the write behind pattern for updating data through the cache. Write behind offers the following benefits over write through:
- The response time and scalability of updates will be decoupled from the database
- Multiple updates to the same entry are coalesced, thus resulting in a reduction in the number of updates sent to the database
- Multiple updates to different entries can be batched
- The application can continue to function upon database failure
In order to configure write behind, modify the <write-delay> setting in the read-write backing map configuration to the amount of time the data should live in the cache ...
Get Oracle Coherence 3.5 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
