Category: Migration

In this post, we explore key strategies and AWS tools to help you successfully migrate your high-throughput relational database while minimizing business disruption.

In this post, we discuss how Heroku migrated their multi-tenant PostgreSQL database fleet from self-managed PostgreSQL on HAQM Elastic Compute Cloud (HAQM EC2) to HAQM Aurora PostgreSQL-Compatible Edition. Heroku completed this migration with no customer impact, increasing platform reliability while simultaneously reducing operational burden. We dive into Heroku and their previous self-managed architecture, the new architecture, how the migration of hundreds of thousands of databases was performed, and the enhancements to the customer experience since its completion.

This is a three-part series in which we discuss the end-to-end process of building a data lake from a legacy SQL Server database. In this post, we show you how to build data pipelines to replicate data from Microsoft SQL Server to a data lake in HAQM S3 using AWS DMS. You can extend the solution presented in this post to other database engines like PostgreSQL, MySQL, and Oracle.

This is the third post in a series where we dive deep into performance testing of MySQL environments being migrated from on premises. In Part 1, we compared the query playback and traffic mirroring approaches at a high level. In Part 2, we showed how to set up and configure query playback. In this post, we show you how to set up and configure traffic mirroring.

This is the second post in a series where we dive deep into performance testing MySQL environments being migrated from on premises. In Part 1, we compared the query playback and traffic mirroring approaches at a high level. In this post, we dive into the setup and configuration of query playback.

In this series of posts, we dive deep into performance testing of MySQL environments being migrated from on-premises to AWS. In this post, we review two different approaches to testing migrated environments with traffic that is representative of real production traffic: capturing and replaying traffic using a playback application, and mirroring traffic as it comes in using a proxy. This means you’re validating your environment using realistic data access patterns.

In this post, we show you how to migrate an Oracle database to an HAQM RDS for Oracle DB instance. The solution uses Oracle Data Pump for initial data load and Oracle GoldenGate Microservices Architecture installed on an HAQM Elastic Compute Cloud (HAQM EC2) instance as the Oracle GoldenGate hub for change data capture.

In this post, we discuss how Phreesia used AWS DMS to replicate their on-premises database to AWS in an effective and cost-optimized manner. Because of the database’s large size and complex data structure, properly tuning the AWS DMS configuration was critical to minimize the migration duration and cost. We outline the fine-tuning techniques that were applied to optimize the AWS DMS task settings, instance size, IOPS provisioning, and table mappings. Applying these performance optimizations allowed Phreesia to develop a migration strategy to move this 30 TB database to HAQM S3 in just 2 days without disruption to production workloads.

With AWS DMS homogeneous migration, you can migrate data from your source database to an equivalent engine on AWS using native database tools. In this post, we show you an example of a complete homogeneous migration process and provide troubleshooting steps for migrating from PostgreSQL to HAQM Aurora PostgreSQL and HAQM RDS for PostgreSQL.

In this post, we show you how to use advanced replication features between MySQL-compatible databases such as HAQM Aurora MySQL-Compatible Edition clusters or HAQM Relational Database Service (HAQM RDS) for MySQL instances. We discuss two replication capabilities in HAQM RDS and HAQM Aurora: multi-source replication and replication filtering. Multi-source replication is supported only in HAQM […]