Blog

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.

Want your application to read from replicas? Here is how to choose the best r/w splitting option available in Tungsten Clustering.

Scalability is necessary to keep your database from crumbling under increased traffic. A scalable database must be able to handle larger data sets and more queries per second (both read and write), and the architecture must support these higher workloads seamlessly and efficiently. This blog attempts to explain what sharding is versus the pod architecture that some of our customers employ.

Recently, a Continuent customer asked: “What is your approach for scaling up MySQL clusters for a higher number of queries per second and larger data sets?” Scaling, like availability, is a multifaceted question. In this blog post we will detail and discuss the best practices for scaling Tungsten Clusters.

People approach Continuent for many reasons, including: MySQL Continuous Operations: their business is using MySQL for business-critical applications that require zero downtime, including for maintenance updates MySQL Performance: their application performance and user experience are suffering due to a faltering MySQL backend MySQL Scaling and geo-scaling: they're scaling up and taking prudent preventative measures to lay a strong foundation based on anticipated growth, within region, cross the regions and

In this MySQL Case Study blog we look at a customer of ours who were able to grow their SaaS business from tens of customers to thousands of enterprise customers once they achieved continuous MySQL operations with Continuent Tungsten.