Blog Series: MySQL High Availability And Disaster Recovery

First we went through an install of a simple three-node cluster using allotted AWS ec2 instances. We created the directories and database users and got the Tungsten Clustering software installed and up-and-running. Then we covered cluster control operations using cctrl, like switch and recover, as well as replicator techniques using trepctl. Some other items on the agenda included an overview of the latest release (which came out last week), replication stages and filters, monitoring, and various useful configurations and options. In Day 2 we learned about backups, and did a deep dive into the various Connector methods and some of their pros and cons.

The Slow Software Movement is spreading with SaaS companies going global...and their software is the furthest from “slow.” In this blog, a Customer Success Manager at Continuent writes about some observations in her five years of listening to customers and prospects.

Real time database replication is a must for clustering and other key business purposes, like reporting. There are a number of replication technologies available for MySQL, and some are even bundled into various solutions. When choosing a replication methodology, it is paramount to understand just how the data moves from source to target. In this blog post, we will examine how asynchronous, synchronous, and "semi-synchronous" replication behave when used for clustering. Also, we will explore how replication affects database performance and data availability.

Why does the DIY approach fail to deliver vs. the Tungsten Clustering solution for geo-distributed MySQL multimaster deployments? Before we dive into the 10 reasons, note why commercially-supported enterprise software is less risky and in fact less costly.

Database Administration is a tough, often ungrateful job. Especially if you run a 24/7 business-critical MySQL or MariaDB deployment.

This blog explains data replication and clustering in a way that anybody can understand.

Our colleague Matt Lang walks you through a comparison of building a global, multi-region MySQL / MariaDB / Percona cloud back-end using AWS Aurora versus Continuent Tungsten.

In case you missed the Multimaster webinar recorded live on Thursday, March 28th, 2019:

Learn how NewVoiceMedia built a global, multi-region MySQL cloud back-end to support a high-volume cloud contact center.

Learn how to build a global, multi-region MySQL / MariaDB / Percona cloud back-end capable of serving hundreds of millions of online multiplayer game accounts:

Watch the Replay

Enterprises require high availability for their business-critical applications. Even the smallest unplanned outage or even a planned maintenance operation can cause lost sales, productivity, and erode customer confidence. Additionally, updating and retrieving data needs to be robust to keep up with user demand.

Think about it - your global, cloud-based application needs to be online and available for the business to run. Downtime is to be avoided like the plague. Perhaps you even have multiple cloud providers to span.

How do we create a database service layer that handles all kinds of failures?