Re: Replication on MySQL databases

2010-11-04 Thread Walter Heck
Classic scenario where MMM will be your best bet. Check out http://mysql-mmm.org for more information. Setup two masters and 2 or more slaves for full High Availability. It scales extremely well if your application is read-heavy (which most applications are). If you need help implementing this, I

Re: Replication on MySQL databases

2010-11-04 Thread Machiel Richards
: Johan De Meersman To: Machiel Richards Cc: mysql mailing list Subject: Re: Replication on MySQL databases Date: Thu, 4 Nov 2010 10:21:11 +0100 If your sites are busy with *writes*, you're kind of stuck. Replication means that every write that happens on one side, also MUST happen on the other

Re: Replication on MySQL databases

2010-11-04 Thread Johan De Meersman
If your sites are busy with *writes*, you're kind of stuck. Replication means that every write that happens on one side, also MUST happen on the other side, so you win nothing. Well, you win a little delay on half of your writes, which is, to most people, really a downside, not an upside. Your bes