Blog

What are some strategies for improving performance when applying to a MySQL target database with Tungsten Replicator?

In this blog post we will define what a split-brain scenario means in a MySQL database cluster, and then explore how a Tungsten MySQL database cluster reacts to a split-brain situation.

Explore the benefits of migrating from Galera Cluster to Tungsten Cluster for MySQL database infrastructure. Learn how Tungsten leverages asynchronous replication for robust performance, overcoming challenges faced by synchronous replication. Discover the ideal architecture for Geo-Scale MySQL clustering and how Tungsten Cluster simplifies deployment with CLI and GUI management tools. Gain insights into achieving high availability, Active/Passive, or Active/Active clusters.

Learn why Aurora Global Database from Amazon may not be a truly global solution for multi-region deployment, and how Tungsten Cluster can help achieve seamless failover in the event of regional outages, without affecting unaffected regions, keeping applications online, and with failback capability.

VMware chose to migrate key MySQL database from Galera (MariaDB Cluster) to Tungsten. In this blog we will look at the key reasons for why VMware ultimately decided that Tungsten Cluster would better fit their multi-site MySQL clusters.

Deploying Composite Active/Active clusters gives end-users the best experience no matter where they are located. Tungsten Cluster makes this possible with the deployment of MySQL clusters at geo-scale, allowing the enterprise to host clusters close to the users. How can we avoid write-conflicts with asynchronous replication and multiple primary databases?

When an application is a primary source of revenue for an organization, keeping Production operations going is critical. This blog discusses three things that can help prevent issues in Production. In fact, that’s why multiple environments exist - to make sure that the final act, delivered in Production, runs smoothly; read on to find out how to make sure your labor is not in vain!

This is the third post in a short series about Tungsten Clustering topologies. In this post we will highlight the key differences between Composite Active/Passive, Composite Active/Active (CAA), and the newly available Dynamic Active/Active topology. In short, DAA blends the simplicity of CAP with the automated continuous operations of CAA.

You’ve seen the recent news about AWS outages; enterprises have to think about where their physical AWS data centers are and treat them as a single point of failure. As such, enterprises running business-critical and mission-critical applications are accounting for geography of public cloud resources in their business-continuity plans. Learn about a solution for continuous operations for your MySQL database that’s a step above traditional MySQL Disaster Recovery (DR).

In this short post we will highlight the key differences between Multi-Site Active/Active (MSAA) and Composite Active/Active (CAA) topologies. The core principle behind an active/active topology is that you have more than one writable cluster. So why do we have more than one type of Active/Active topology?

Galera Cluster provides high availability and scalability for MySQL. While this provides high availability in a local region or site, it does not provide any provisions for disaster recovery (DR) or any multi-site deployment in general, so let’s explore how we could extend the functionality of Galera Cluster to deploy at geo-scale.

This blog takes a look at three stacks: networking, LAMP, and the modern MySQL database clustering stack. The networking stack is a foundational element of geo-distributed MySQL database services. LAMP is a common software solution stack used by web and other client-server applications. The modern database clustering stack enables multi-site, multi-region and globally distributed MySQL database systems for continuous operations, which Tungsten Clustering provides in a complete, fully-integrated and tested package.