We often hear that asynchronous replication creates a possible data loss window, thus it is not an acceptable solution for certain types of applications.
Yes, this is true. In theory, that is.
In practice, we have developed the Tungsten Cluster solution to the point that it really does not happen in real life. Please read this blog to understand why not!
Application performance and MySQL database responsiveness is always high priority for highly-available, business-critical use cases. That’s why Tungsten Clustering offers features and options to tune for maximum performance, such as Parallel Apply. When does Parallel Apply work best? What are the limitations? To find out, read this blog from MySQL industry vet, Eric M. Stone, the COO of Continuent!
This blog post looks at the ins and outs of Amazon Aurora replication and how to best go about that; including all the details you need to replicate to and from Aurora with the Tungsten Replicator AMI.
Amazon Redshift has been providing scalable, quick-to-access analytics platforms for many years, but the question remains: how do you get the data from your existing datastore into Redshift for processing? This blog looks at that question by providing some background information on Redshift replication as well as details on how to easily replicate from MySQL to Redshift.
It’s Hadoop’s 15th birthday and we’re looking at how to easily replicate from MySQL to Hadoop and why in this blog on real-time big data analytics.
Read about MySQL to MongoDB / MongoDB Atlas replication: what it’s all about, why it’s needed and how it works.
In this blog post, we explore how the two new Tungsten Replicator roles allow for THL transfer when not actively extracting or applying events. This new behavior provides for better control and performance under a variety of conditions.
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.
