Open
Description
From http://books.couchdb.org/relax/reference/high-performance
There is a pattern for reliable storage using batch mode. It=92s the same=
pattern as is used when data needs to be stored reliably to multiple nodes=
before acknowledging success to the saving client. In a nutshell, the appl=
ication server (or remote client) saves to Couch A using batch=3Dok, and th=
en watches update notifications from Couch B, only considering the save suc=
cessful when Couch B=92s _changes stream includes the relevant update. We c=
over this pattern in detail in the Replication chapter.
I didn't see any coverage of this pattern in other chapter!
token=40859aae6b9645cadaaa9f68d22b1800login=janl