Hi, i'm a new user of couchdb. my company is developing a SaaS app that relies completely on json manifest to work, so couchdb was perfect for the task. We expect a heavy load (100K users), so the replication is a very important feature for us and like it was promoted that replication was easy on couchdb, we finally decided to use it.
Before subscribing to the mailing list, i supposed that master -> master replication was a good option, removing the failure point of having only one write master at a time, but i just saw that exist's "leaf" revisions where the data is not consistent between masters. so i have a couple of questions, about this: 1) what is the best setup to assure consistency? write-only masters to read-only slaves like common node setups? Even that performance is really important we need to prevail consistency on top of everything. 2) we don't need revs at all, all changes are final. reducing rev_limit value has a positive impact on performance? if it has, what is the recommended value? 3) like the wiki said that ssl was not supported correctly by erlang, we set up an haproxy in the frontend that forward the request to the couchdb http. like is the first time we work on a DB system with an http frontend (and not a permanent connection like mysql or redis) what is the recommended setup in terms of network? (like timeout, keep alive options etc..). any documentation about this is useful. Any advice regarding on this is highly appreciated ! Regards.
