17 Mar
2010
17 Mar
'10
4:33 p.m.
Neil Aggarwal wrote:
Our goal is to create redundancy. We want either system to be able to work if the other is not available. Designating one database as a write db and the other as a read defeats that.
Depending on the requirements splitting out can greatly improve scalability though, potentially using something like mysql proxy and perhaps even a load balancer.
The write systems can still be clustered/multi-master replication but if the bulk of your work is reads then load balancing many independent databases for reads can improve performance and even improve availability.
But it really depends on the workload.
nate
--
This message has been 'sanitized'. This means that potentially
dangerous content has been rewritten or removed. The following
log describes which actions were taken.
Sanitizer (start="1268843612"):
Split unusually long word(s) in header.
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
Match (names="unnamed.txt", rule="9"):
Enforced policy: accept
Total modifications so far: 1
Anomy 0.0.0 : Sanitizer.pm
$Id: Sanitizer.pm,v 1.94 2006/01/02 16:43:10 bre Exp $