Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of mark@van-cuijk.nl designates
 79.170.90.37 as permitted sender)
From: Mark van Cuijk <mark@van-cuijk.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Questions on durability
Message-Id: <55CCE097-9D63-4E28-8873-698AB57822E8@van-cuijk.nl>
Date: Tue, 23 Apr 2013 21:37:32 +0200
To: user@couchdb.apache.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))

Hi,

For a new project, we're considering CouchDB as an interesting candidate =
for storage, mainly because of the good durability properties, support =
for replication and the continuous changes feed.

Regarding durability I have three questions. I found the durability =
matrix on the wiki, but the page isn't finished yet. Our setup will be a =
single client writing to a single CouchDB server, which is replicated to =
several other CouchDB servers.

1. Can I access the continuous changes feed on each of the servers and =
will those feeds serve the same events in the same order?
2. Will each server only send events to the changes feed after the data =
is durably persisted to hardware storage?
3. The batch=3Dok parameter influences the response to the writing =
client, but does it have any influence regarding the answer to the =
previous question?

Thanks,
Mark=