Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of adam.kocoloski@gmail.com
 designates 209.85.219.215 as permitted sender)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v1076)
Subject: Re: massive replication?
From: Adam Kocoloski <kocolosk@apache.org>
In-Reply-To: <ccb631ed0910231227oca7784er9ebfe7798aff2273@mail.gmail.com>
Date: Fri, 23 Oct 2009 15:32:31 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <1FADCCC0-EE66-48A9-8B70-8C331DFE0EFB@apache.org>
References: <4AE2028F.9030502@meetinghouse.net>
 <ccb631ed0910231227oca7784er9ebfe7798aff2273@mail.gmail.com>
To: user@couchdb.apache.org

On Oct 23, 2009, at 3:27 PM, Andrew Melo wrote:

> On Fri, Oct 23, 2009 at 2:22 PM, Miles Fidelman
> <mfidelman@meetinghouse.net> wrote:
>> A couple of the recent CouchDB powerpoint presentations illustrate
>> replication across massive numbers of database instances.  Does that
>> represent anything remotely possible, for real?
>> We have an application that involves replicating data across very  
>> large
>> numbers of nodes that are intermittently connected - where we'd like
>> collections of data to replicate and synchronize as connectivity  
>> allows.
>>  Think something like USENET news as an analogy.
>
> Hey Miles,
>
> I don't know if it would fit your needs (I've not used it personally),
> but this may be worth looking into:
>
> http://tilgovi.github.com/couchdb-lounge/
>
> Thanks,
> Andrew

Lounge is very cool, but it's more suited to distributing very large  
datasets over a smallish number of always-connected couches.  Miles'  
situation is tailor-made for CouchDB's replication model.  Best,

Adam