Caution!! If any one of them dies and cannot be recovered, you will have a
mess to fix.
From: Prabhat Kumar [mailto:aim.prab...@gmail.com]
Sent: Wednesday, May 30, 2012 1:43 PM
To: Rick James
Cc: Anupam Karmarkar; Nigel Wood; mysql@lists.mysql.com
Subject: Re: Architectural Help
Hi Anupam
immune to floods, tornados, cyclones, power outages, motherboard death, etc.
>
> > -Original Message-
> > From: Anupam Karmarkar [mailto:sb_akarmar...@yahoo.com]
> > Sent: Thursday, May 24, 2012 3:39 AM
> > To: Nigel Wood
> > Cc: mysql@lists.mysql.com
> &
t: Thursday, May 24, 2012 3:39 AM
> To: Nigel Wood
> Cc: mysql@lists.mysql.com
> Subject: Re: Architectural Help
>
> Dear Nigel,
>
> Thank for reply..
>
>
> See my comments below
>
>
> --Anupam
>
>
>
> From:
Dear Nigel,
Thank for reply..
See my comments below
--Anupam
From: Nigel Wood
To: Anupam Karmarkar ; "mysql@lists.mysql.com"
Sent: Thursday, 24 May 2012 3:35 PM
Subject: RE: Architectural Help
A few questions:
which is more or a proble
A few questions:
which is more or a problem: network outages, network capacity or query latency?
When you say "near real-time" do you need transactional consistent view on all
49 servers or can some lag be tolerated?
Can any one of the 49 local servers potentially update/delete the same rows or
is the central database server just ONE server, to which all your 50 data
center app connects
On Thu, May 24, 2012 at 2:47 PM, Anupam Karmarkar
wrote:
> Hi All,
>
>
> I need architectural help for our requirement,
>
>
> We have nearly 50 data centre through out different cities from these data
>
