I’ll be presenting a webinar next Wednesday, January 23 at 10 a.m. (Pacific Time), about issues application developers should think about for scaling out read-query traffic using multiple MySQL instances in a replication pair.
Specifically, about the care we have to take because replication is asynchronous. This means the slave may not have current data at all times, so an application must choose to query the slave or the master dynamically. As much as possible, we’d like to automate this choice so that application developers can be the most productive.
Please join me for this webinar by registering here: https://www.percona.com/webinars/readwrite-splitting-mysql-and-php
A very interesting topic indeed, esp. when you start throwing into the mix update queries and transactions.
I’d love to have the split happens transparently in a layer below the application (eg. the php mysql-nd driver), but for having worked on the code which implements this feature in eZ Publish, I know it can get hairy
I forwarded this to my development colleague who recently wrote a loadbalancing layer for our SaaS platform. Might be interesting for him.