Why ScaleDB?

MySQL has evolved from supporting fast but simple websites, to supporting far more complex and powerful applications. Based on its penetration of the web market, it was a no brainer that it would become the dominant cloud database as well. However, the current MySQL storage engines were not designed to deliver the high-availability (HA) demanded by enterprises, or the elasticity required in the cloud. ScaleDB extends MySQL into enterprise and cloud applications by adding these capabilities, while maintaining the compatibility and performance of MySQL.

MySQL is the fastest growing database in the world because of its lower total cost of ownership (TCO) and its flexibility. One powerful example of MySQL’s flexibility is the ability to select the storage engine that is ideally suited for your application. Considering your application’s requirements for availability, transactions, read and update performance, and more, you can select a storage engine that addresses your specific needs. In fact, we have created a storage engine selector that allows you to select the ideal MySQL storage engine for your application.

Why would you select the ScaleDB storage engine? If your application has any of the following requirements, you should seriously consider ScaleDB for MySQL:

  • Cloud elasticity (add/remove nodes on the fly to accommodate shifting usage patterns)
  • Large numbers of concurrent users
  • Large data sets
  • Large numbers of tables with complex relationships (e.g. using joins, materialized views, etc.)
  • ACID compliant transaction processing
  • Load balancing (e.g. to address temporal shifts in usage patterns)
  • High-availability with smooth fail-over
  • An evolving application with changing data storage requirements
  • Lower Total Cost of Ownership (TCO)
  • Large numbers of CPUs/cores you are trying to saturate

ScaleDB for MySQL leverages two advances that combine to make it significantly better than alternatives for large scale applications. These two advances are shared-disk clustering and multi-table indexing. You can read more about these capabilities in the Technology page.