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 markjreed@gmail.com
 designates 74.125.82.54 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=pfKi1kHp7AfcBpyjtYd3GdzZLAeUusMTpkArEl1wa/fu2LBvwjUSUcZvRrzSckO0bU
         aOiMPY7Wn5Fnxi9zdE3ak6Xojyl8fuwmzDqnvPbYwmMiTh7sYHutkJ9OndZXdH4lTdkU
         CnEGzYzqpOIQXX7ngTng/0wSFZfw6NkRuutc8=
MIME-Version: 1.0
In-Reply-To: <AANLkTimiQwJyqnon=ULRiGTHsn0DE=CXvxz90Ey=qiGF@mail.gmail.com>
References: <AANLkTi=wTLG9CNWnU_XGoc1FCJ8fOPmes2A0bgQN3TZq@mail.gmail.com>
	<3AAAF2E5-5345-4192-BC94-51ED931C9827@vpro.nl>
	<AANLkTimiQwJyqnon=ULRiGTHsn0DE=CXvxz90Ey=qiGF@mail.gmail.com>
Date: Fri, 29 Oct 2010 10:47:14 -0400
Message-ID: <AANLkTi=m7W_aq+-r+6diewMv077wvE82ru6nL8Avcq3w@mail.gmail.com>
Subject: Re: Why use multiple databases ?
From: "Mark J. Reed" <markjreed@gmail.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Another consideration is data churn rate. If you have a set of
documents that are changed or deleted frequently, such as login
session data, you might want to put them in their own database and
compact it more often than the database with the relatively static
content.

On Friday, October 29, 2010, Zachary Zolton <zachary.zolton@gmail.com> wrot=
e:
> I'd also like to add that permissions are a common reason to put docs
> into separate databases. For example, if each user should only see
> there own docs, then you should give each user their own database.
> (Given that CouchDB can only enforce read permissions at the database
> level.)
>
> On Fri, Oct 29, 2010 at 4:07 AM, Nils Breunese <N.Breunese@vpro.nl> wrote=
:
>> Op 29 okt 2010, om 10:37 heeft Zdravko Gligic het volgende geschreven:
>>
>>> (1) What kind of issues do you take into consideration when deciding
>>> if certain types of documents should go into their own database ?
>>
>> It makes sense to store all documents used by an application in the same=
 database. That way your data can be easily replicated along with your desi=
gn documents. Only start separating data into different databases when ther=
e is a real need. If you can't explain why you need multiple databases, jus=
t start with a single one. Relax, you can always split out later.
>>
>>> (2) Are your decisions based on performance, security or some other
>>> considerations ?
>>
>> No. (But maybe somebody else's are?)
>>
>>> (3) What else should I be asking you - if I was not a noob ;?)
>>
>> I have no idea.
>>
>> Nils.
>> ------------------------------------------------------------------------
>> =C2=A0VPRO
>> =C2=A0phone: =C2=A0+31(0)356712911
>> =C2=A0e-mail: info@vpro.nl
>> =C2=A0web: =C2=A0 =C2=A0www.vpro.nl
>> ------------------------------------------------------------------------
>>
>

--=20
Mark J. Reed <markjreed@gmail.com>