From user-return-13407-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Fri Oct 29 14:39:34 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 49288 invoked from network); 29 Oct 2010 14:39:33 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Oct 2010 14:39:33 -0000 Received: (qmail 80942 invoked by uid 500); 29 Oct 2010 14:39:32 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 80706 invoked by uid 500); 29 Oct 2010 14:39:31 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 80697 invoked by uid 99); 29 Oct 2010 14:39:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Oct 2010 14:39:30 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of zachary.zolton@gmail.com designates 74.125.82.42 as permitted sender) Received: from [74.125.82.42] (HELO mail-ww0-f42.google.com) (74.125.82.42) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Oct 2010 14:39:24 +0000 Received: by wwi18 with SMTP id 18so4250854wwi.5 for ; Fri, 29 Oct 2010 07:39:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=8CIcHztxZPldB5ityzCl7D6YTjWoCl92+IZvlaW1V3k=; b=w4WBA8aZX27EXapT/f724Qk6eeLg/Mg1saghU9e5yrT7Me1HGAxr9UbitinWyT29Im HjWBhQNulGdCR6fLjYsxrNST1Kbq7a8OGiEiD2M+yPRURXGmKc/okGS611fksqhLHm7E I1lWYffWPx5onMXjA2IBFcGKNU2JV42KDbTsA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=t5fcRIEFHiOx0h49/ruSRoELCvgEr7XT1jHWjCsSIc0imrkA0leDdNA2PRxBk/7k6v XXZp6e/F60XOR8n0jLu26c+aaksCu7/oZXwXGn9hPiGcRpDGv6rZxuu4/HmMSV37Lbks RTS10tM5JIY3+wpJja+kJC2BJ61ZpRCJhuMaY= Received: by 10.227.133.72 with SMTP id e8mr7373583wbt.109.1288363142977; Fri, 29 Oct 2010 07:39:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.69.2 with HTTP; Fri, 29 Oct 2010 07:38:42 -0700 (PDT) In-Reply-To: <3AAAF2E5-5345-4192-BC94-51ED931C9827@vpro.nl> References: <3AAAF2E5-5345-4192-BC94-51ED931C9827@vpro.nl> From: Zachary Zolton Date: Fri, 29 Oct 2010 09:38:42 -0500 Message-ID: Subject: Re: Why use multiple databases ? To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 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 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 desig= n documents. Only start separating data into different databases when there= is a real need. If you can't explain why you need multiple databases, just= 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. > ------------------------------------------------------------------------ > =A0VPRO > =A0phone: =A0+31(0)356712911 > =A0e-mail: info@vpro.nl > =A0web: =A0 =A0www.vpro.nl > ------------------------------------------------------------------------ >