On Apr 4, 9:28 pm, Roberto Spadim <robe...@spadim.com.br> wrote: > i'm using repcache without problem, if one server die the other have > the same information, when other server is up it's automatic sync with > the 'master' > it works well with php memcache session handler > but a good session handler could be a nosql database (membase) since > it's not a cache, it's a database...
Membase doesn't currently have cross datacenter master/master replication that can compensate for inconsistencies introduced by network outages or latency when a user is jumping back and forth between two data centers. Anything that *can* is going to be much slower. I think Brian's got it there. Your best bet is to keep the users contained where networks are fast. RTT between SF and VA is something like 20ms. Replication doesn't help the situation. You might as well pin the data for the user in one data center and just fetch it across the country every time (which is effectively what AP systems will do).
