In this blog, we discuss Galera Cluster and synchronous versus asynchronous replication. We also discuss some of the differences between Galera Cluster and Tungsten Cluster rooted in this difference in foundation. And how Tungsten has served a critical niche - mission-critical, geo-distributed, highly-performant MySQL applications - for a long time.
There are two key elements (which often separate us from many other open source operators, such as Percona) to our MySQL HA/DR and Continuous Operations solutions. Read this blog, adapted from the June “Word from the CEO” from the Continuent Newsletter to find out what distinguishes Continuent’s Tungsten Clustering solution in the open source MySQL database industry.
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!
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.
