This next blog in our Continuent MySQL Case Study series is a sub-series on the topic of ‘multi-master MySQL’, in which we cover three multi-master MySQL use cases focusing on e-commerce to start with, financial services and telecommunications.
Over the past few days we have been working with a number of customers on the best way to handle Triggers within their MySQL environment when combined with Tungsten Replicator. This new blog dives head first into the minefield of Triggers and Replication.
Performing schema changes often requires extended downtime for applications. This is due to MySQL needing to rebuild tables for common schema change operations. Tools like pt-online-schema-change have been written to try to overcome the downtime associated with schema changes, however they are complex and put a high load on the database.
