over 7 years ago

Best practices for migrating RDS for MySQL databases to Amazon Aurora

There are three weeks remaining in the Amazon Aurora challenge. Submissions are due November 5, 2018 before 5pm ET. Be sure to get started on your submission and remember, once you submit a project, you can keep editing it as needed at any time prior to the submission deadline.

Best practices for migrating RDS for MySQL databases to Amazon Aurora

MySQL is the most popular open-source database in the world. However, many customers find that the undifferentiated heavy lifting of backups, high availability, and scaling of MySQL databases to be complex, time-consuming, or both.

This is one of the leading reasons why customers move their existing MySQL footprint to Amazon RDS for MySQL. Amazon RDS provides features like point-in-time recovery and high availability options right out of the box. RDS for MySQL even supports five read replicas for each source. With these, you can easily scale read workloads without having to manually configure and maintain binary log (binlog) replication.

If you want MySQL compatibility with the performance and availability of high-end commercial databases, you can migrate your MySQL databases to Amazon Aurora. With Amazon Aurora with MySQL compatibility, you can take advantage of features like fast database clones and autoscaling replicas. You also get native integration into other AWS services like AWS Lambda and Amazon CloudWatch Logs. In addition to those features, Amazon Aurora also offers enhanced durability by replicating data across three Availability Zones. It also can scale to 15 Aurora Replicas, all within latency often less than 20 milliseconds.

In this blog post, we will look at how to migrate from Amazon RDS for MySQL to Amazon Aurora MySQL with minimal downtime.

Read the Full Blog Post Here >>

Questions?

If you have any questions about the hackathon, please post on the discussion forum.