Read this blog to learn about replication between MySQL and Apache Kafka: what it’s all about, how it works, and the tools to use to make it work smoothly.
In this second post on real-time data replication from MySQL, MariaDB or Percona Server we’re looking at PostgreSQL replication, for example with one practical application using a POD style deployment with MySQL.
This blog discusses Asynchronous versus Synchronous MySQL replication for MySQL clustering. Synchronous replication is viewed as the ‘holy grail’ of clustering. But unfortunately, when something is too good to be true, it often is. Before the Tungsten cluster solution Continuent built two synchronous replication cluster solutions (m/cluster, uni/cluster), but we abandoned those for good reasons.
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.
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.
This month we’re celebrating our 4th - or is it our 20th? - anniversary: read about our history and where we are today on the path to more years of MySQL availability and continuous operations.
On Monday April 27th, MySQL released a much anticipated patch release 8.0.20. Along with many bug fixes and improvements, a new property was introduced - binlog-transaction-compression. During our own testing we have discovered an incompatibility with this property. Read on for more information.
An overview of a Tungsten topology that doesn’t get much attention: the Cluster-Slave, which is an easy way to get data resiliency and integration, with features that make it ideal for big data analytics, reporting, and backups.
Watch this 30min training video on how to get started with Tungsten Replicator AMI and how to avail of it on Amazon Marketplace; including a step-by-step demonstration.
Over the past few days we have been working with a number of customers on the best way to handle Triggers within their MySQL environment when combined with Tungsten Replicator. This new blog dives head first into the minefield of Triggers and Replication.
Start your free 14-day trial of the new Continuent Tungsten Replicator (AMI) - the most advanced & flexible replication engine for MySQL, MariaDB & Percona Server, including Amazon RDS MySQL and Amazon Aurora.
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.
