Blog

For the sixth in the Competitor Comparison series in which we look at the main solutions for MySQL high availability, disaster recovery and geographic distribution, I got a chance to interview Matt Lang, Customer Success Director, Americas at Continuent. We focused on highly available, geo-scale, multi-region MySQL for mission-critical sites and apps with Do-it-Yourself (DIY) solutions as compared to MySQL clustering with Continuent Tungsten, the only complete, fully-integrated clustering solution for MySQL - on-premises, in the cloud, hybrid-cloud or multi-cloud.

This is the fifth blog in our ‘High Noon’ comparison series in which we look at the main solutions for MySQL high availability, disaster recovery and geographic distribution. Here we focus on highly available, geo-scale, multi-region MySQL for mission-critical sites and apps with Oracle’s InnoDB Cluster as compared to MySQL clusters with Continuent Tungsten, the only complete, fully-integrated clustering solution for MySQL - on-premises, in the cloud, hybrid-cloud or multi-cloud.

We’ve just recently brought our Tungsten Cluster (AMI) up to the current release level of our flagship product, Tungsten Cluster, and would like to invite users to give it a test drive!

Join the replay of this webinar which discusses the use of geo-distributed active/active MySQL clusters for Telco providers, and on how to cost-effectively provide worldwide mobile roaming access with cloud-based Tungsten MySQL clusters.

How to build a multi-region, multi-master MySQL cloud database back- end capable of serving a global, high-volume cloud contact center: this global SaaS provider is a Cloud Contact Center solution provider, who needs to deliver up-to-date data to clients as quickly as possible.

For this next ‘multi-master MySQL’ blog in our Continuent MySQL Case Study series, we’re focussing on Financial Services Saas providers.

This blog explains why the Tungsten rollback error exists and why it's important.

In this blog post we will discuss how the managed cross-site replication streams work in a Composite Multi-Master Tungsten Cluster for MySQL, MariaDB and Percona Server.

From time to time we are asked how to check whether or not there are data discrepancies between Master/Slave nodes within a MySQL (or MariaDB) cluster that's managed with Tungsten Clustering.

This blog covers INI vs Staging configurations for Secure Shell.

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.

A robust monitoring setup is essential for cluster health and viability - if your replicator goes offline and you do not know about it, then that Replica becomes effectively useless because it has stale data. This means keeping a close watch on the health of the MySQL / MariaDB / Percona Server database nodes from many perspectives, from ensuring sufficient disk space to testing that replication traffic is flowing.