Real-Time MySQL Analytics: In this first in a series of blog posts on real-time data replication from MySQL, MariaDB or Percona Server to high-performance data analytics engines (and how to do so easily and cost-effectively with the Tungsten Replicator AMI), we’re focussing on Vertica replication.
This is the first blog in our ‘High Noon’ comparison series in which we look at the alternative solutions for MySQL high availability, disaster recovery and geographic-distribution. We focus on highly available, geo-scale, multi-region MySQL for business critical applications as directly compared to Amazon Aurora. Tungsten Clustering makes it easy to deploy and manage highly available MySQL clusters with any version of MySQL, MariaDB, and Percona Server for MySQL on-premises, in the cloud, hybrid-cloud or multi-cloud.
Performing MySQL schema changes often requires downtime for applications. In this blog, we cover two ways we can perform MySQL schema changes without risking downtime or other MySQL data problems. In this real-life customer example, we perform a schema change to modify the column data type from varchar(20) to varchar(50) on approx. 35 tables from 3GB to 10GB in size. Two of the tables are partitioned, and one of them is about 100GB combining all partitions for that table.
What is the difference between MySQL replication and MySQL clustering? While clustering involves a layer of replication, the capabilities, benefits, and reasons for using clustering versus replication are very different. At Continuent, we offer both clustering and replication for your MySQL, MariaDB, and Percona MySQL - in the cloud, on-prem, hybrid-cloud and multi-cloud, with no application changes or downtime necessary.
“We don’t take backups, we use replication instead.” If you happen to agree with this statement, I urge you to continue reading. But even if you think you have a good backup plan, I still urge you to continue reading. Taking backups is usually not one of the most exciting parts of the job, but it might be the part that saves your company from a catastrophe. So, let’s make a plan!
Disaster Recovery for Continuous MySQL Operations does not have to be hard, but it does have to be WAN: Multi-Site, Hybrid-Cloud, Multi-Cloud. This blog discusses Business Continuity, Disaster Recovery, or “DR,” and an overlooked clustering feature that makes continuous database operations easy, affordable, and manageable.
This blog provides a refresher outline of what’s involved in our Tungsten Cluster Competitive Comparison program and Tungsten Cluster highlights as well. Read on and find out why Tungsten Cluster is a better and more cost-effective overall MySQL HA/DR/Geo-Scale solution compared to other options in the market.
Get a better MySQL HA/DR solution at a lower cost - Tungsten Cluster - the value is compelling: Introducing the Tungsten Cluster Competitive Upgrade Program!
View this presentation to learn about two types of (MySQL) database proxies, which we refer to as ‘fast & simple proxy’ and ‘intelligent proxy’; and how transparent failover and read-write splitting works for these.
Continuent is pleased to announce the 6.1.4 versions of its Tungsten Clustering and Tungsten Replicator software products for MySQL, MariaDB and Percona Server.
The new releases introduce support for the MySQL 8.0.20 binlog compression feature, improvements and fixes to command line tools, and more.
We’re also announcing the release of Tungsten Dashboard 1.0.8.
Version 6+ of Tungsten Clustering comes with a host of improvements for your Multi-Site Multi-Master topology (MSMM); this is partly why it has a new name: Composite Master-Master (CMM). Probably the most notable improvement is that the Managers are more aware. What does that mean?
This blog article discusses why and how we use Ansible (automation tool for pre-configuring MySQL servers) for Tungsten purposes at Continuent, including a step by step description on how to use Ansible (including source code).
