-
Book Overview & Buying
-
Table Of Contents
Oracle Coherence 3.5
By :
The pattern of accessing the cache exclusively for reading data can be extended for writing data as well. Write through inherits all of the benefits associated with read through, but it adds a few of its own as well, which are as follows:
A single point of data update simplifies the handling of concurrent updates.
While write through is synchronous by default, it could easily be made asynchronous by changing a configuration option, which will be covered in the next section.
The biggest benefit of synchronous (as opposed to asynchronous) writes is that failed operations to the database will cause the cache update to roll back, and an exception will be thrown to the client indicating the failure of the store operation.
Prior to Coherence 3.6, the default handling of write through failure was to log the exception on the storage cluster member and allow the cache write to succeed. In order to propagate the store exception to the client and roll back the cache update, the <rollback...
Change the font size
Change margin width
Change background colour