> 3. Use couchdb in a single-writer multiple-reader scenario. If you only do > that for those activities that require uniqueness then you have consistency > issues to deal with because replication is asynchronous. One way to do that > is to switch a session to the writable server as soon as you need > uniqueness. The single writer becomes a bottleneck, but this is what I'm > doing because it matches my information architecture.
Not necessarily something you'd ever want to do yourself, but the Facebook engineering blog describes their approach to this scenario (different problem, similar space). http://www.facebook.com/note.php?note_id=23844338919
