Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 423AB97CB for ; Fri, 11 May 2012 05:25:26 +0000 (UTC) Received: (qmail 12653 invoked by uid 500); 11 May 2012 05:25:24 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 12229 invoked by uid 500); 11 May 2012 05:25:16 -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 12004 invoked by uid 99); 11 May 2012 05:25:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2012 05:25:15 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of googcheng@gmail.com designates 209.85.213.52 as permitted sender) Received: from [209.85.213.52] (HELO mail-yw0-f52.google.com) (209.85.213.52) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2012 05:25:08 +0000 Received: by yhpp61 with SMTP id p61so2855671yhp.11 for ; Thu, 10 May 2012 22:24:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=3g5483uKAApl2emQD+9+dJgNaeZ8cY0R9sZ7Qba8iHA=; b=r+YwjBXNZA3rNbwtg9x7fn4KMbXCLfVaZjJrAWhxmkOMWK/YFaNzPIneAmQsgw47NY zxfbmj+qpWqbRiPNUzyDaK3hCmJYiQAJ+Kwkb+EnE0V2Gvy9+K+HAJJEX2gf1snmxbJC roZNjDZfcYfhrzImvMsvSc1HEBXDHDbn0JLM/unQCVNHJoqOZZdo+knfHUyvnqDiSMdu Xzzk4wGgt9ONW8FFd2I+9ei0t/KGHZP14Se1BT+B+XqyIAlGl1BVbrEYEEnZp6F29xEY qwcToaW0cjEKQTpOqR2BY8HyZzN6+rpugDXTU0HfKVNeVWSR96STRESr5SXphEPMOrfH UEeA== MIME-Version: 1.0 Received: by 10.236.191.40 with SMTP id f28mr8501136yhn.115.1336713887573; Thu, 10 May 2012 22:24:47 -0700 (PDT) Received: by 10.101.55.17 with HTTP; Thu, 10 May 2012 22:24:47 -0700 (PDT) In-Reply-To: <001a01cd2edb$2dcbd120$89637360$@maf.org> References: <001001cd2e2f$99298c70$cb7ca550$@maf.org> <001801cd2ec1$c02e5480$408afd80$@maf.org> <001a01cd2edb$2dcbd120$89637360$@maf.org> Date: Fri, 11 May 2012 13:24:47 +0800 Message-ID: Subject: Re: Library System in production From: goog cheng To: "user@couchdb.apache.org" Content-Type: multipart/alternative; boundary=20cf303f6d706f65bb04bfbbf44c --20cf303f6d706f65bb04bfbbf44c Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable are they relax for the multi-user environment =D4=DA 2012=C4=EA5=D4=C211=C8=D5=D0=C7=C6=DA=CE=E5=A3=ACRobert Wadholm =D0= =B4=B5=C0=A3=BA > How many users/clients are you expecting? CouchDB itself scales quite wel= l > as far as the size of the DB is concerned (especially in the numbers of > files you are talking about). It also scales well for numbers of > synchronous > users/clients, though if needed you can look at BigCouch for increased > scalability as far as that is concerned I think (you can create a couch i= n > the cloud). If documents or attachments are relatively stable (not being > changed excessively often--like every couple of seconds), performance is > quite high. Of course, your application will need to be built to scale > well--check out the CouchDB guide online for a starter on how couch (and > your app) can scale: http://guide.couchdb.org/draft/scaling.html. > Bob > > > > > > I forgot something. > > How scalable is CouchDB for enterprises applications in a library with > thousands and thousands of files > > > --20cf303f6d706f65bb04bfbbf44c--