- Products & Solutions
- About Us
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.
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.