MySQL Replication has become an essential component of scale-out architectures in LAMP environments. When there is a necessity to scale out, MySQL offers a multitude of solutions, the most common being to add read replicas. The major bottleneck for our data is generally not so much oriented around writing our data but more around reading back this data. Therefore the easiest way to scale MySQL is to add replicas for reading.

And with today’s cloud environments, where resources are dynamically allocated and deallocated, systems need the ability to automatically adapt to sudden changes. For MySQL Replication, this includes tasks like detecting failures, promoting a slave to master, failing over slaves, and so on. A load balancer with Virtual IP can also help mask topology changes from the application, and dispatches read and write traffic appropriately.

With that in mind, we’d like to introduce the Severalnines Blueprint for MySQL Replication, a new whitepaper which discusses all aspects of a MySQL Replication topology with the ins and outs of deployment, setting up replication, monitoring, upgrades, performing backups and managing high availability using proxies as ProxySQL, MaxScale and HAProxy.

The MySQL Replication Blueprint is about having a complete ops-ready solution from end to end including:

  • Installation and configuration of master/slave MySQL servers, load balancers, Virtual IP and failover rules
  • Management of the topology, including failure detection, failover, repair and subsequent reconfiguration of components
  • Managing topology changes when adding, removing or maintaining servers
  • Managing configuration changes
  • Backups
  • Monitoring of all components from one single point

This whitepaper discusses the following core topics in depth:

  • Why the need for a Replication Blueprint
  • Introducing the MySQL Replication Blueprint
  • Monitoring
  • Management
  • Load Balancing

Get your free copy of our new whitepaper

Related Post