Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of theflinnster@gmail.com
 designates 209.85.217.10 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer;
        b=USbg7KOcummrM9ZAU3J4MFRQMSLw2G2EbzX/iNcrKnOHNQVmnkbGZ/fdiG+lnm3vvq
         gO736xKxdf8c8Rsj1FKpz4pCbMePKRlwZIbf4DSNuB0yIH1At9UPoOGwUi012v7CJ1nQ
         biMUV2XWwiMHHRZM9uDoY1BAtNB4j9/5fdH4U=
Message-Id: <2D2F5D7F-FAC7-44C9-A43C-C6135AADC743@gmail.com>
From: Flinn Mueller <theflinnster@gmail.com>
To: user@couchdb.apache.org
In-Reply-To: <C58E34D4.148F6%kurt@arstechnica.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Considerations for lots and lots of databases?
Date: Sat, 10 Jan 2009 13:15:40 -0500
References: <C58E34D4.148F6%kurt@arstechnica.com>

Kurt, what language/framework are you planning to use for the project?

On Jan 10, 2009, at 12:19 PM, Kurt Mackey wrote:

> I really, really like not having to deal with schema updates.  Given  
> that I don't have to worry about this in quite the same way with  
> Couch, I've been wondering what the downsides are to splitting data  
> into multiple databases on a SaaS project.  The idea is that each  
> account/customer would get their own database, rather than simply  
> marking documents with an "owner".
>
> Now, the obvious downside is that it makes it more difficult to do  
> cross-customer queries.  But what other problems are there with this  
> idea?  Assuming that there were lots and lots and lots of accounts,  
> what performance implications are there to giving each their own DB  
> rather than making them all share?
>
> -Kurt