Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 35712 invoked from network); 23 Oct 2009 23:43:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Oct 2009 23:43:19 -0000 Received: (qmail 80045 invoked by uid 500); 23 Oct 2009 23:43:18 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 79977 invoked by uid 500); 23 Oct 2009 23:43:18 -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 79961 invoked by uid 99); 23 Oct 2009 23:43:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2009 23:43:18 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=FS_REPLICA,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates 209.85.160.56 as permitted sender) Received: from [209.85.160.56] (HELO mail-pw0-f56.google.com) (209.85.160.56) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2009 23:43:08 +0000 Received: by pwi18 with SMTP id 18so2378133pwi.35 for ; Fri, 23 Oct 2009 16:42:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=3AwvB30sRFCocGiLVPO3NJcnxM3ssAwY8fQBPZRlObY=; b=TilmfoD63IVwxduJPeKP3vMc5rxJxKljZrnyYZf680yDrqxZMuhAJRTGSHDUB3Zp7I Lr1lxwT46oovSb/+/YGH1OP3CF7QoDJyd3GWxZ0sKBeRaDhhK/nlJvKvNoWsSjVNpJ4N IlMntAW+2ZZb+X9oPkwwilydIOlypMg6p8AhQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=g+LrtbWMtmB2jpe43KGtaUuOyCRudsL3hIeO3BRG3aGrYKsIFBAmGzBHShRzJeI4+Y hgQSYt9SkTU9kDcOpZXvSSED4voH89J/Fq9kVtjUGaXSI0QxzESk6+Iqx5d9Bj48ZC/9 kFmqiqatxVnOS5K9A/rALj13QgOm9dooBiPXs= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.143.24.41 with SMTP id b41mr941685wfj.238.1256341367124; Fri, 23 Oct 2009 16:42:47 -0700 (PDT) In-Reply-To: <4AE2247B.1010803@meetinghouse.net> References: <4AE2028F.9030502@meetinghouse.net> <0C6A665F-53C0-41ED-9A8E-C00098B45174@apache.org> <4AE20CD6.7010500@meetinghouse.net> <4AE2247B.1010803@meetinghouse.net> Date: Fri, 23 Oct 2009 16:42:47 -0700 X-Google-Sender-Auth: d345f43afaea35d7 Message-ID: Subject: Re: massive replication? From: Chris Anderson 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 On Fri, Oct 23, 2009 at 2:47 PM, Miles Fidelman wrote: > Daniel Tr=FCmper wrote: >> >> Hi, >> >>> 2. It seems like there's a point at which explicit 1-1 replication star= ts >>> to be an administrative nightmare. =A0Some kind of publish-subscribe or >>> multi-cast update model seems needed. >> >> Would the new continuous replication feature be what you need? With this >> all changes to A get automatically replicated to B, if I get things righ= t >> here... > > Well it's more of, when I change A, I want the changes to propagate to B > through Z (or "all") - with some sort of multi-cast addressing rather tha= n > having to identify every node explicitly. If you do a hub-and-spoke or ring topology you can simplify the replication problem a bit. But a gossip protocol is more resistant to down nodes. I'd like to see a replication bus in the open source project. However, continuous replication will pretty much work. > > -- > In theory, there is no difference between theory and practice. > In practice, there is. =A0 .... Yogi Berra > > > --=20 Chris Anderson http://jchrisa.net http://couch.io