Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 71174 invoked from network); 20 Dec 2008 14:39:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Dec 2008 14:39:52 -0000 Received: (qmail 26392 invoked by uid 500); 20 Dec 2008 14:39:51 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 26361 invoked by uid 500); 20 Dec 2008 14:39:51 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 26350 invoked by uid 99); 20 Dec 2008 14:39:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Dec 2008 06:39:51 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.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; Sat, 20 Dec 2008 14:39:42 +0000 Received: from [192.168.2.7] (i59F4D808.versanet.de [::ffff:89.244.216.8]) (AUTH: LOGIN jan, TLS: TLSv1/SSLv3,128bits,AES128-SHA) by jan.prima.de with esmtp; Sat, 20 Dec 2008 14:39:20 +0000 Message-Id: <65E53DA1-51DA-420C-A792-494F45A0200C@apache.org> From: Jan Lehnardt To: dev@couchdb.apache.org In-Reply-To: <7d8fb2e90812200601v5652f1d2hd52997786639514f@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Subject: Re: Multi-database application: is that possible? Date: Sat, 20 Dec 2008 15:39:20 +0100 References: <7d8fb2e90812200601v5652f1d2hd52997786639514f@mail.gmail.com> X-Mailer: Apple Mail (2.929.2) X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 20 Dec 2008, at 15:01, Andrea Schiavini wrote: > Hallo! > I've been recently thinking about the possible different design > choices > offered by CouchDB, and - more generally - by Document Oriented > Databases. > Specifically, I considered the case of web applications like > Amazon.com, > where they need to have full consistency in some specific "fields", > like > item availability; They actually don't. Enforcing consistency at their size is a lot more expensive than saying: "Sorry, we know we told you you can buy this, but we were wrong, here's a $20 cupon for your next purchase." > still, in the biggest part of their database (the one > about item descriptions, user details etc.), they can get huge > benefits from > a document oriented database. > How do they solve the problem of consistency? I think a good > solution could > be to use a two-database design, with a standard SQL database to > store only > item availability and critical data, and another document oriented > database > for everything else. Of course, a cross database relation has to be > built. > I've read that SimpleDB by amazon also offers eventual consistency, > like > CouchDB; and they also state that they're using SimpleDB for the > amazon.comwebsite. So, how do they solve this problem? Amazon's CEO Werner Vogels describes their system in detail: http://www.allthingsdistributed.com/2007/10/amazons_dynamo.html Cheers Jan --