How To Maintain Consistency Between Cache And Database With Write-Behind CacheStore erase/eraseAll Being Executed Asynchronously and store/storeAll Being Executed Asynchronously (Doc ID 1934453.1)

Last updated on FEBRUARY 24, 2017

Applies to:

Oracle Coherence - Version 3.7.1.1 and later
Information in this document applies to any platform.

Goal

Consider the following scenario:

  1. Put new entity object with key 1
  2. Remove new entity object with key 1
  3. Put new entity object with key 1


How does a Coherence CacheStore configured with write-behind verify that the delete (remove), which is supposed to be executed synchronously, does not fail because the previous insert (put of new existing object), which is supposed to be executed asynchronously, had not been executed yet?

How does Coherence maintain consistency between cache and database state in such scenario?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms