Discover Tungsten Clustering for MySQL - In Its New Setting
We’ve created a new space on our website for our flagship product Tungsten Clustering. This blog invites you to take a tour of the new product section and to get in touch with us for your MySQL MySQL High Availability, Disaster Recovery and/or Geo-Clustering needs.
Use Case: MySQL HA and Disaster Recovery
This MySQL high availability and disaster recovery use case is based on a customer of ours who is a government-regulated lottery service and who needs 24x7x365 operations as well as be able to perform maintenance without any disruption to their public facing gaming website.
Watch the Webinar Replay: How to build a $10M SaaS business into a $6B Unicorn with MySQL and Continuent Tungsten
Watch the replay of this webinar hosted by Database Trends & Technologies (DBTA) and presented by Continuent CEO Eero Teerikorpi: How to build a $10M SaaS business into a $6B Unicorn with MySQL and Continuent Tungsten.
Case Study: Continuous MySQL Operations for Growing SaaS Business
In this MySQL Case Study blog we look at a customer of ours who were able to grow their SaaS business from tens of customers to thousands of enterprise customers once they achieved continuous MySQL operations with Continuent Tungsten.
Case Study: MySQL High Availability, Zero Downtime Maintenance and Disaster Recovery for SaaS
This is the second post in a series of MySQL case study blogs. It discusses a SaaS provider dealing with sensitive medical data and their need to be able to quickly deploy clusters in AWS and recover from multi-zone AWS outages.
Tungsten Clustering Makes The 2020 DBTA Top Trending Products List
We’re delighted to be able to share that Tungsten Clustering - our flagship product - is named in the DBTA 2020 List of Trend Setting Products!
Geo-Scale MySQL for Continuous Global Operations & Fast Response Times
This is the first in a series of use case blogs. It discusses the concept of ‘Geo-scale MySQL’ - or how to build a global, multi-region MySQL cloud back-end capable of serving hundreds of user accounts.
Comparing Replication Technologies for MySQL Clustering: Part 1
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.
Read the White Paper: Tungsten Clustering for MySQL, MariaDB & Percona Server Databases
Read our white paper on Tungsten Clustering for MySQL, MariaDB and Percona Server. Tungsten Clustering allows enterprises running business-critical database applications to cost-effectively achieve continuous operations on a global scale.
10 Reasons Why Tungsten Clustering Beats the DIY Approach for Geo-Distributed MySQL Deployments
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.
Blog from the Top -- What keeps you up at night? Sleep better with Continuent!
Database Administration is a tough, often ungrateful job. Especially if you run a 24/7 business-critical MySQL or MariaDB deployment.
In a proxy-ed world, where do connections come from?
Database Proxies provide a single entry point into MySQL for the calling client applications. Proxies are wonderful tools to handle various situations like a master role switch to another node for maintenance, or for transparency with read and write connections. However, when the time comes to perform the switch action, all of the calling clients have been funneled through the proxy, so identification of the calling host from the database itself becomes difficult.