Database Tiering

Achieving Scale-Out by Combining MySQL
with your Existing Database

Many organizations are facing a double threat of increasing volumes of data and transactions while at the same time needing to reduce their IT organizations' resources. As a result, many are turning to a new, modern scale-out architecture that is built on using low-cost commodity Intel / Opteron hardware running an open source LAMP (Linux, Apache, MySQL, PHP / Perl / Python) stack.

While many might advocate migrating existing database applications to an open source solution, there may be practical reasons to not undertake such migration projects. Is there an architecture that enables organizations to keep their current database systems running as-is while adding open source to the solution? Yes, in fact the notion of "database tiering" has become a common way for many IT organizations to add open source software to provide greater cost-effective scale-out while minimizing change to existing systems.

The concept behind database tiering is the seamless co-existence of multiple (legacy and new) database technologies to best solve a business problem. In many cases, legacy systems and databases are difficult to replace in one step. At the same time, legacy database infrastructures pose exponential cost problems and may limit options to accommodate further growth.

By using a database tiering methodology, MySQL can complement existing database infrastructures and allow IT organizations to scale-out their data processing capabilities effectively at a low cost. When placed at the front-end of legacy systems, the MySQL database co-exists with existing databases by means of data synchronization.

既に MySQL.com アカウントをお持ちの方はすぐにログインできます。