Tungsten Clustering - Key Topologies

A “Cluster of Clusters” where one cluster contains the single active, writable primary. All other clusters and nodes are passive and read-only. Typically two or more clusters.

In the Tungsten Composite Active/Passive Cluster topology (Active/Passive), there is a single writeable primary node across all sites, and all writes are directed to that primary. The Connectors are multi-site aware and will automatically react to a site failover. Replication flows in one direction only, from the current active primary cluster to the passive DR cluster(s).

This topology provides a highly-available local operations and an active failover site that is also available for reads. It is well-suited for customers who seek the highest level of HA, with the ability to operate applications on both sites, without application changes.

The Active/Passive Tungsten Clustering solution is for SaaS providers, e-commerce companies, financial services providers, gaming companies and telco providers who are seeking five-9s availability for their business-critical and mission-critical MySQL applications.

A “cluster of clusters” where all clusters contain a writable primary. Typically two or more clusters.

In the Tungsten Active/Active Cluster topology (Active/Active), there is one writeable primary node per cluster, and all writes are directed to that primary by the local Connectors. The Connectors are able to use any other site in the event of a local outage; both sites are write-able at all times, and each cluster replicates from all other member clusters.

This topology links highly-available clusters across sites to enable constant availability for updates in two locations separated by high-latency networks.

The Active/Active Tungsten Clustering solution is perfect for those business-critical and mission-critical MySQL applications that require lower latency for local updates while still needing to maintain completely geo-distributed data sets for Disaster Recovery needs. It is recommended for SaaS applications, credit card payment gateways, or online services that must always be available for business.

The Tungsten Clustering HA configuration is designed for sites that strive to ensure constant availability. The standalone cluster is the basic building block that provides easy high availability to your applications without requiring any changes. This topology ensures the ability to perform maintenance on any database server and still maintain an environment capable of HA failover at all times.

Tungsten Clustering is an ideal solution for SaaS providers with Pod Architecture. It provides an excellent HA solution with infinite scalability. Just by adding more clusters, SaaS providers can serve more customers.

Tungsten Clustering HA with Read Scaling is ideal for sites that require HA and read-scaling for enhanced performance under peak loads. Tungsten Clustering enables the use of the replica nodes to support additional read traffic without impacting cluster performance. Media and consumer web sites should consider this option.

Tungsten Clustering with extra read replicas is for the business-critical MySQL applications with high read/write ratio.