couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthew Gamble <>
Subject Design Question
Date Sun, 06 Dec 2009 22:01:24 GMT
I'm been trying to wrap my head around how to layout my application in
couchDB for the past few days and I can't seem to figure out which is the
best way of doing it.  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.

In a nutshell, I'd like to store addresses (VCard like data) for users.  My
first thought was a single document per-user with each VCard as an
attachment but that made it very hard to search the data as it required the
client side to download and parse everything for a search.

My next idea was a document for each VCard and a key (user_id, for example)
to denote which user the card belongs to.  This is quick to access with a
view, and might be the right way to do this?

Or is it best to put each user as their own database and store the address
books / VCards as documents?

To give you an idea of the scale, I'm looking at 100-200k unique users with
(up to) 5000 VCards each.  I really like the idea of using CouchDB to store
the address book / vcard data as it lets me only enter the data that's
actual used.

Thanks in advance for any advice - like I said, I'm still trying to wrap my
head around the way CouchDB works.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message