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 arojis@gmail.com designates
 209.85.214.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=vUZptEIhv4M5pW8N2ZP1S3bsPfj6NzTTyOy/IaSOW8397+xeT6KS9u+AArxolfQGIS
         lLE3eTSh9ZS3s6nHrxLJ6c+xg/QjiOqNBL4gkxkHLnLYMuh47wXWpQalACJ8pzSKs8iB
         3s+W0svC8lQ7PzH8mZvtIcHHJsaq84l8iTpjU=
MIME-Version: 1.0
Date: Fri, 15 Apr 2011 22:15:34 +0530
Message-ID: <BANLkTikQpjTrkTrVXBFo1juVDE=b51B51A@mail.gmail.com>
Subject: Multi-tenancy in Couch
From: Aroj George <arojis@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0015174c19925669b804a0f7c59a

--0015174c19925669b804a0f7c59a
Content-Type: text/plain; charset=ISO-8859-1

Hi,

What's the best way to implement multi-tenancy in couch?

In the sql world you could choose to do either a tenant id key in every
table or separate schemas for each tenant or even separate database
instances...

Similarly in couch i guess you can store each tenant's document in a
separate database. This seems a very simple option.
But then is there a max limit on the number of databases we can create in
couch?

The other option, not too hard either, is to have the tenant id as the first
key in all the views and use the startkey to filter out the tenants.

Will greatly appreciate if you can share your thoughts on which approach is
ideal and will scale better.
Or if there are more approaches that I have not thought off.

Rgds,
Aroj

--0015174c19925669b804a0f7c59a--