Why multi-master replication?
Master-slave configuration is a great solution when your system is read-bound. But what happens if you want to support high write loads while keeping the option to select the data using a single SQL statement?
Multi-master replication is the solution for that. However, there are several methods in the market for that, and when choosing the right method, you should carefully define your needs: a synchronous method or an asynchronous one, row-based or statement-based (traffic between servers) and if time-delayed replication is required (for quick recovery from delete for example).
The Multi-master Replication Options
I just kicked off the first Israeli MySQL User Group in association with Wix this week, and I wanted to share with you Michael Naumov's presentation from our first event.
In his talk, Michael presented four methods to support multi-master replication: MySQL 5.6 Native, NDB, Tungsten and Galera.
Careful selection of the right MySQL multi-master replication can save you production issues and can boost your system. Now all that's left is to define what is needed and what the matching solution is for that.