MySQL Enterprise Edition
Distributed, Scalable, Highly Available
MySQL Replication enables users to cost-effectively deliver application performance, scalability and high availability. Many of the world's most trafficked web properties like eBay, Facebook, Tumblr, Twitter and YouTube rely on MySQL Replication to serve hundreds of millions of users and handle exponential growth.
MySQL Replication is easy to provision, allowing for simple Master/Slave topologies through to complex chained clusters achieving massive scalability.
New! MySQL 5.6 Replication
MySQL 5.6 introduces the most extensive set of replication enhancements ever delivered, enabling MySQL to serve your most demanding web, cloud, social and mobile applications.
Scale-Out with MySQL Replication
Using MySQL Replication, organizations are able to scale out their applications on commodity hardware by distributing their data across MySQL server farms, within and across data centers and regions. This gives users the flexibility to elastically add or remove instances to dynamically adjust capacity based on demand.
In addition, long running jobs such as analytics workloads can be offloaded to slaves, allowing masters to be dedicated to serving real-time transactional workloads.
High Availability with MySQL Replication
By mirroring data between instances, MySQL replication is the most common approach to delivering High Availability for MySQL databases.
In addition, the MySQL replication utilities can automatically detect and recover from failures, allowing users to maintain service in the event of outages or planned maintenance.
Managing MySQL Replication
MySQL Enterprise Monitor includes the Replication Monitor, which provides a visual dashboard to manage replicated MySQL servers. Using the Replication Monitor organizations get a consolidated, real-time view into the health, performance and availability of all replication topologies. Plus, the Replication Advisor Rules help DevOps and DBAs to proactively identify and address any Replication related issues such as Master/Slave performance and latency issues, before they can become costly outages.