Multi-master replication provides redundant copies of your most important business assets. What’s more it allows applications to scale out, which is perfect for cloud hosting solutions like Amazon Web Services.
But when you decide you need to scale your write capacity, you may be considering active-active setup. This is dangerous, messy and prone to failure. We’ve outlined how.
Click through to the end for multi-master solutions that work with MySQL.
Reason 1 – auto_increment introduces new problems
o MySQL’s auto_inc settings make it more difficult to change servers around in your overall replication topology
o Using auto_inc settings can cause MySQL to introducing gaps in your primary keys which is a waste of space
o Such a solution would require all tables to have auto_inc primary keys