Hi Patrick, thats a nice article and actually we are doing something similiar here. But I have one question: If all your reads are being sent to the slaves, how do you cope with delayed slaves in your perl application? Especially with the following...
See more 
Hi Patrick, thats a nice article and actually we are doing something similiar here. But I have one question: If all your reads are being sent to the slaves, how do you cope with delayed slaves in your perl application? Especially with the following program flow: receive post parameters, update values in DB (master), read values from DB (slave), send data to browser. If you have seconds-behind-master of only 1 second this might lead to problems. Example: User changes something in his profile and clicks "submit". Your perl program does some sanity check of the values, then updates the user's profile in the DB, then reads the complete profile from the local slave and generates the answer. But the local slave is 1 second behind, so the saved values are not yet replicated and you fetch the old data and present this to the user (ok, this one is easy: you keep the changed values in your programm and send those back. But consider a bit higher seconds-behind-master and a click happy user who... See less 
.value, '<a href="http://www.kaboodle.com/steveo/mysql-master-master-repl.html"><img alt="" src="http://cn1.kaboodle.com/hi/img/2/0/0/113/7/AAAAAoxqiaUAAAAAARNx9g.png" width="100px" /></a>','http://www.kaboodle.com/steveo/mysql-master-master-repl.html','1');)
