I should note that BC (and cloudant.com, even more so) generally contain more than the advertised couchdb release.
On 4 Jul 2012, at 14:11, Simon Metson wrote: > IIRC it's currently built of v1.0.2 > > > On Wednesday, 4 July 2012 at 13:49, Gabriel Mancini wrote: > >> Hi Guys any one knows if bigcouch works on couchdb 1.2 ? >> >> On Wed, Jul 4, 2012 at 3:11 AM, Mathias Leppich <[email protected] >> (mailto:[email protected])> wrote: >> >>> Already had a look on BigCouch? http://bigcouch.cloudant.com/ >>> >>> - Mathias >>> >>> On Jul 4, 2012, at 3:21 , Michael Parker wrote: >>> >>>> Given that CouchDB is a multi-master system, it seems that reads scale >>>> gracefully while writes do not -- because N reads among k nodes can be >>>> spread as N/k reads per node, while N writes among k nodes requires >>>> each of the nodes to perform all N writes. >>>> >>>> So what's the best practice on scaling writes? Clearly each node >>>> should not be responsible for performing all N writes and we would >>>> want to partition the data storage. I was thinking of consistent >>>> hashing, but that requires some logic to merge results from views. My >>>> best idea so far is to partition documents based on their type, and >>>> all documents of a given type exist in the same partition. >>>> >>>> Is http://guide.couchdb.org/draft/clustering.html current, or is there >>>> something else I should be looking at? Anyone have any success stories >>>> to share? >>>> >>>> Guidance would be much appreciated! Thanks! >>>> >>>> - Mike >> >> >> -- >> Gabriel Mancini de Campos >> Arquiteto de Soluções >> >> +55 (11) 9449-1706 >> [email protected] (mailto:[email protected]) >> São Paulo - SP - Brasil >> >> > >
