MySQL replication blueprint

The MySQL Replication Blueprint white paper includes all aspects of a Replication topology with the ins and outs of deployment, setting up replication, monitoring, upgrades, performing backups and managing high availability using proxies.

What we’ll cover in this white paper

• 1. Introduction
• 2. Why a Blueprint for Replication?
  • 2.1. Replication in the pre-MySQL 5.6 era
  • 2.2. Making MySQL Replication Production Ready
  • 2.3. GTID – A Stronger Foundation for Replication
• 3. Introducing the MySQL Replication Blueprint
  • 3.1. Deployment
  • 3.2. Master/Slave
  • 3.3. Multi Master
  • 3.4. Parallel replication
  • 3.5. Multi source replication
  • 3.6. Management & Monitoring
  • 3.7. Load balancers
• 4. Monitoring
  • 4.1. Availability
  • 4.2. Performance
  • 4.3. Alerting
• 5. Management
  • 5.1. Replication topology changes
  • 5.2. Adding new slaves
    • 5.2.1. Why would you delay a slave?
  • 5.3. Repairing a broken replication topology
    • 5.3.1. Slave promotion
    • 5.3.2. Most advanced slave without GTID
    • 5.3.3. Most advanced slave with GTID
    • 5.3.4. Automated slave promotion
  • 5.4. Backups
    • 5.4.1. Logical or physical backups?
    • 5.4.2. Do you need full or incremental backups?
    • 5.4.3. Scheduling
    • 5.4.4. Testing your backups
  • 5.5. Updating to a newer version
  • 5.6. Schema changes
  • 5.7. Configuration changes
• 6. Load Balancing
  • 6.1. What are the benefits of proxies?
  • 6.2. Read/Write splitting
  • 6.3. Which proxy to choose?
  • 6.4. Query Caching
  • 6.5. Query rewrites