Return-Path: X-Original-To: apmail-couchdb-marketing-archive@minotaur.apache.org Delivered-To: apmail-couchdb-marketing-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6A5FC17561 for ; Wed, 6 May 2015 18:49:50 +0000 (UTC) Received: (qmail 49464 invoked by uid 500); 6 May 2015 18:49:50 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 49431 invoked by uid 500); 6 May 2015 18:49:50 -0000 Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: marketing@couchdb.apache.org Delivered-To: mailing list marketing@couchdb.apache.org Received: (qmail 49419 invoked by uid 99); 6 May 2015 18:49:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 May 2015 18:49:50 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.191.145.13 which is an MX secondary for marketing@couchdb.apache.org) Received: from [54.191.145.13] (HELO mx1-us-west.apache.org) (54.191.145.13) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 May 2015 18:49:43 +0000 Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com [209.85.213.169]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 3DC7922F8F for ; Wed, 6 May 2015 18:49:23 +0000 (UTC) Received: by iget9 with SMTP id t9so104179369ige.1 for ; Wed, 06 May 2015 11:47:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=uwkIm1Fn2qb+bz3KI8xK7qLaxRs4B8pFfEQJl4C9Oy0=; b=bq/nYtkKt9ANixdNDMTUuuOe5/VmXl9u5IPb5Q1sDEWI+5t0RFnJCbjaEP4lgb6kIT nHLHz6ls9GhmAhfnd2lnPiBVtNOnwQi7op3HrKgjns0pw4z050cwuj2Xwaooj03X8CAY 11zlYZbsIrU4x6HSYz1EMl6QyU0D9bdW9Xftjtlzq6Gnan3bnsMjsQaUvkropR+u209K KndEOtbzaw3ZI7NKJZqcI4HLigOKzsLzrgYKLaSbgh5cwBGAv0cOsrwmaBODZ34p2YWW 0+KUlew1AdPV7/i6HV5Ug+cEbsu38I4RGCATVi4DCTmzbR5d5IFEzklVgoSf5PP8N7jP n+Wg== X-Received: by 10.43.133.137 with SMTP id hy9mr3959330icc.74.1430938072497; Wed, 06 May 2015 11:47:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.66.5 with HTTP; Wed, 6 May 2015 11:47:31 -0700 (PDT) In-Reply-To: <76FDAF2E-820D-4EC6-AA41-1B1E27407F52@apache.org> References: <9340C895-279C-46A1-9596-3B370F83AAED@apache.org> <554A472F.3000908@meetinghouse.net> <76FDAF2E-820D-4EC6-AA41-1B1E27407F52@apache.org> From: ermouth Date: Wed, 6 May 2015 21:47:31 +0300 Message-ID: Subject: Re: How do CouchApps fit into the CouchDB story? (Was: CouchDB Articles, Pills and Tutorials Ideas) To: marketing Content-Type: multipart/alternative; boundary=20cf307f331681e5cd05156e3b7c X-Virus-Checked: Checked by ClamAV on apache.org --20cf307f331681e5cd05156e3b7c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Sure, but how is that conceptually different? Well... Imagine doc with 100 attaches in CouchDB and then 101 object in Riak. Now, compare them in these situations: 1. What happens when replication breaks in the middle? 1. How we can determine it happened? 2. What can we do with half-updated data? 2. You need atomic update of 50 attaches >> life I=E2=80=98d say reasonable limit for Riak blob is about 10-20 Mb) > Same in CouchDB, really. He-he, you underestimate CouchDB ) ermouth --20cf307f331681e5cd05156e3b7c--