I would suggest reading this:
http://guide.couchdb.org/draft/replication.html
1.) It is a key feature to CouchDB not to rely on centralized (master-slave)
replication, but you could build it with CouchDB
Peer-To-Peer by definition does exclude centralized servers (well, I
think).
2.) I think if two CouchDB's cover each other, replication should work as well,
as there is just the same port in use for everything.
Regards,
Chris
On 06.04.2011, at 20:13, Zdravko Gligic wrote:
> OK, lets start with some basic questions ;)
>
> (1) How would two CouchDB go about discovering and meeting each other?
> Would this not require a central server (similar to IRC) and are
> there any hosted solutions?
>
> (2) Once at least two CouchDB's discover and meet each other, is it
> just their URLs (domain name or IP based) that are needed? What about
> routers and/or firewalls?
>
> Thanks again.
>
>
> On Tue, Apr 5, 2011 at 1:36 PM, Zdravko Gligic <[email protected]> wrote:
>> Hi Folks,
>>
>> Are there any large implementations of CouchDB peer-to-peer
>> replications or even smaller open source samples? Actually, the piece
>> that I am mostly interested in is at the application/design end of how
>> to go about implementing the "traffic cop" for a use case where
>> everyone is eventually synchronized with everyone else.
>>
>> Given a large number of peers that one could replicate to/from, is
>> there anything within CouchDB that can be "posted centrally" to know
>> how up to date anyone is, so that badly out of date peers are
>> replicate to/from the more up to date ones, instead to/from each
>> other? What else should I ask, if I knew better ;?)
>>
>> Thanks,
>> Zdravko
>>
