On Tue, Jan 27, 2009 at 8:38 AM, Wout Mertens <[email protected]> wrote: > Hi there, > > I'm a big fan of CouchDB and I want to use it in production but I'm holding > out for a somewhat stable release. In preparation however I would like to > know where CouchDB stands in High Availability and/or Scalability. > > I know that Erlang promises that you can run a single program across > multiple CPUs and even systems at the same time, and you can upgrade the > program while it is handling requests. I presume Erlang also handles the > case where a system goes offline? > > Furthermore, I know that the view server runs separately from the CouchDB > process, and it can in principle split the map and reduce phases across many > compute nodes. > > Finally, I know that the replication works. Is there a "standard" way of > using it with supporting programs? > > > So my question is: How much of this is already a reality? Is any testing > being done for these scenarios? Is this on the roadmap for 1.0? > > Thanks, > > Wout. > >
Just thought I'd mention that this article came across my google alerts today and it's actually related to the original thread: http://www.joeandmotorboat.com/2009/01/27/couchdb-load-balancing-and-replication-using-haproxy/ There are people doing some fault tolerant multi-node setups. The different articles I've read all tend to have one guiding theme, "Holy shit, that was easy!" Anyway, I think the best way to figure out if CouchDB is up to snuff for what you're wanting, the best thing is to setup some simulated load and see if shit hits the fan. :) We're always excited to hear numbers on different load types and configurations. HTH, Paul Davis
