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 jens@couchbase.com designates
 206.225.164.28 as permitted sender)
From: Jens Alfke <jens@couchbase.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Date: Thu, 6 Sep 2012 16:05:27 -0700
Subject: Re: App layer on top of replication
Thread-Topic: App layer on top of replication
Thread-Index: Ac2MhBsa29lnWi5+RKOAahyy0TZmOw==
Message-ID: <D54EAEA1-8E76-4739-A2ED-8DF6FE9AFC74@couchbase.com>
References: 
 <CAO8ppXf_NTPuiKXK4UGwCq2kvY8mDpJAFXd633kA4PeQ-b21Ag@mail.gmail.com>
In-Reply-To: 
 <CAO8ppXf_NTPuiKXK4UGwCq2kvY8mDpJAFXd633kA4PeQ-b21Ag@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_D54EAEA18E764739A2ED8DF6FE9AFC74couchbasecom_"
MIME-Version: 1.0

--_000_D54EAEA18E764739A2ED8DF6FE9AFC74couchbasecom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


On Sep 6, 2012, at 1:41 PM, Eduardo Scoz <eduardoscoz@gmail.com<mailto:edua=
rdoscoz@gmail.com>> wrote:

My idea is to put CouchDB behind something like Nginx or NodeJS that would
intercept direct calls to the database, but still let replication work (as
described above). all_docs replication would also have to be disabled, I
guess.

What makes this tricky is that document contents leak out through other API=
 calls besides direct GETs of a doc URL. For instance, you can look at all =
documents by getting the _changes feed or _all_docs, and of course querying=
 views. Your proxy layer would have to be aware of these =97 for example it=
 would have to block any requests for _changes unless they specified a filt=
er that restricted the results to docs that user can see (or maybe it could=
 rewrite the URL to add such a filter?)

I think this is do-able but it=92s the sort of thing where I=92d worry that=
 someone will come up with some creative use of the API to get around it.

A proposed solution by the couchbase guys is to have multiple databases,
one for each user, and then use replication to share the data, but this
seems unmanageable to me once you get thousands of users syncing docs
around.

It depends on your data model. At one extreme, if users=92 data is entirely=
 private, the user databases will all be independent and there=92s no overh=
ead. How much data is shared between your users?

=97Jens

--_000_D54EAEA18E764739A2ED8DF6FE9AFC74couchbasecom_--