|
From: Vladimir S. <vst...@gm...> - 2012-07-30 16:49:26
|
On Mon, Jul 30, 2012 at 6:35 PM, Vladimir Stavrinov <vst...@gm...> wrote: > I see only way to provide read & write LB simultaneously if replication > will be done asynchronously in background process. This way we should > have a distributed database as main stock accomplished with numbers of > replicated nodes containing complete data. In such system read requests > should go to replicated nodes only when they are up to day (at least for > requested data). Asynchronous updates in such architect should support > LB for write requests to distributed nodes, which should remain > synchronous. Such architect allow to create totally automated and complete LB & HA cluster without any third party helpers. If one of the distributed (shark) nodes fails, it should be automatically replaced (failover) with one of the up to date replicated nodes. |