Building and maintaining complex distributed systems
June 19–20, 2017: Training
June 20–22, 2017: Tutorials & Conference
San Jose, CA

Best practices for MySQL high availability

Colin Charles (Percona)
9:00am–12:30pm Tuesday, June 20, 2017
Distributed Data & Databases
Location: LL21 A/B
Level: Intermediate
Average rating: ***..
(3.00, 1 rating)

Who is this presentation for?

  • SREs, DBAs, and DevOps engineers

Prerequisite knowledge

  • A working knowledge of MySQL replication (preferably in an environment with more than three replicas)

Materials or downloads needed in advance

  • A laptop (Linux or MacOS preferred; Windows machines must have access to a Linux box via SSH or the ability to run Docker)

What you'll learn

  • Explore the current MySQL high-availability landscape


The MySQL world is full of trade-offs; choosing a high-availability solution is no exception, but only with high availability can you achieve distributed systems in your database layer. Colin Charles explores the MySQL high-availability landscape, offering deep dives into current technologies, recommendations, and what to look out for.

Topics include:

  • MySQL replication
  • MHA
  • DRBD
  • Tungsten Replicator
  • Galera Cluster (and variants like Percona XtraDB Cluster and MariaDB Galera Cluster)
  • NDB Cluster
  • ProxySQL (with comparisons to MariaDB MaxScale and MySQL Router)
  • Semi-sync replication
  • Orchestrator
Photo of Colin Charles

Colin Charles


Colin Charles is the chief evangelist at Percona. Previously, Colin was on the founding team of MariaDB Server, worked at MySQL, and worked actively on the Fedora and projects. Colin has been a MySQL user since 2000. He’s well known within open source communities in APAC and has spoken at many conferences.

Leave a Comment or Question

Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?

Join the conversation here (requires login)