Update run on master node?
What would be the best approach to route requests in a couchbase environment to the couchbase server that is acting as a master for a piece of data?
The reason I ask is that my "Game" object has grown to be 450 kb (after some serious tweaking of the JSON, it was originally 2.5 MB). I'm worried about sending that data over and over to the various web servers just so they can do an update and send it back over. JSON compresses well, but I wasn't sure if the objects are transferred via text or some form of compression (GZIP?).
Is this something I should be concerned about, or am I over complicating the situation?
Likewise, is the best approach to have couchbase on dedicated servers or should each website have its own instance of the couchbase server? (One approach leads towards specialized nodes and the other is obviously very conductive to cloud deployment and scalability where every server is the "same").