couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Anderson <>
Subject Re: Design Question
Date Mon, 07 Dec 2009 00:04:49 GMT
On Sun, Dec 6, 2009 at 2:48 PM, Matthew M. Gamble <> wrote:
> Thanks Roger!
> If I go down the "one user, one DB" path is there a limit to the number of databases
I can create?  Any performance issues with having 100k+ unique databases?

Couch has been tested and works fine with millions of databases. If
you need to spread them across directories, create them with a "/" in
the name (properly escaped in the url, of course) and couch will
create subdirectories to hold the files.

> ------Original Message------
> From: Roger Binns
> To:
> ReplyTo:
> Subject: Re: Design Question
> Sent: Dec 6, 2009 5:25 PM
> Hash: SHA1
> Matthew Gamble wrote:
>> I'm sorry if a question like this has been asked
>> before, but I couldn't find anything in the archives that was quite the same
>> as what I'm trying to do.
> There indeed was a similar discussion.  One of the final conclusions was
> that it would be best to have each user plus their data stored in a separate
> DB.  The reason for this is that it makes the security rules easier to
> define and also makes more sense for replication.  (Presumably you want to
> eventually allow the users to run a personal CouchDB with the same database.)
>> attachment but that made it very hard to search the data as it required the
> May be helpful
>> Or is it best to put each user as their own database and store the address
>> books / VCards as documents?
> That would be most natural.  In theory you can write an update handler that
> parses the vCard into fields and makes them keys of the doc.  If you do this
> then the full text search should work really easily.
> Roger
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla -
> Za4An3KylQT6Z788a09Nr1MOH2jiXeFU
> =AJpY
> Sent from my BlackBerry device on the Rogers Wireless Network

Chris Anderson

View raw message