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?
Avoiding Conflicts with Multi-Primary Clusters
Geographic Distribution and Geo-Scale