Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 18290 invoked from network); 9 Feb 2009 14:56:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Feb 2009 14:56:10 -0000 Received: (qmail 44201 invoked by uid 500); 9 Feb 2009 14:56:08 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 44167 invoked by uid 500); 9 Feb 2009 14:56:08 -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 44156 invoked by uid 99); 9 Feb 2009 14:56:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2009 06:56:08 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.97.50.139] (HELO jan.prima.de) (83.97.50.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2009 14:56:00 +0000 Received: from dahlia.lan (f053003027.adsl.alicedsl.de [::ffff:78.53.3.27]) (AUTH: LOGIN jan, TLS: TLSv1/SSLv3,128bits,AES128-SHA) by jan.prima.de with esmtp; Mon, 09 Feb 2009 14:55:38 +0000 Message-Id: <6FD5B222-065D-4201-AAA0-E3D471F806C4@apache.org> From: Jan Lehnardt To: user@couchdb.apache.org In-Reply-To: <5186956f0902090643m74511f66rf4a68778569871f8@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: The Blog Date: Mon, 9 Feb 2009 15:55:06 +0100 References: <5186956f0902082052m43546a8dmb6d9a3ebf9685034@mail.gmail.com> <5186956f0902090228p5a6db266l764fde4c82b571d0@mail.gmail.com> <5186956f0902090338i2829df1erebaa24a4feea7e06@mail.gmail.com> <5186956f0902090449s76befd76g4cf9ded9f59efc86@mail.gmail.com> <5186956f0902090627y1239b12es505ee80b2d6bd248@mail.gmail.com> <5186956f0902090643m74511f66rf4a68778569871f8@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) X-Virus-Checked: Checked by ClamAV on apache.org On 9 Feb 2009, at 15:43, Mister Donut wrote: >> Actually that's not true. We aren't using a system like SimpleDB >> where your changes might not be immediately available in subsequent >> queries by the same user. > > Isn't the point of replication to handle massive reads? If so, you'd > be using load balancing? So you cannot predict which server will be > chosen? Read-scaling is _a single_ possible application. And this would work just the same way e.g. MySQL read scaling would work and there are several ways other smart people handled that case for their use-case; plenty of sources to steal from. All this is very application specific again and cannot be solved in a general case. Also, see Damien. Cheers Jan --