I totally agree with the sentiment of the post - using CouchDB has simply been unbelievable amounts of fun (and certain types of applications would be painful if not impossible to design without it).

The existence of projects like couchdb-python and couchdb-lucene are just icing on a very tasty cake.

I'm not too familiar with multi master replication. What happens when a request handled by server A is followed by a subsequent request that is routed to server B before server A has replicated the changes from the first request? The client would expect a certain state on the "server" given the first request but it certainly seems possible to invalidate that.

Great writeup. I use CouchDB behind nginx anyway for simple authentication so I'll have to try this. The only problem is "continuous replication currently does not survive server restart" - that is not so good.