Google Cloud: Fully Launches AlloyDB for PostgreSQL and Database Migration Services

[This article is compiled and published by Cloud Ace. Cloud Ace is a global strategic partner of Google Cloud. It has more than 300 engineers and is also the highest level partner of Google. It has won Google Cloud Partner Awards many times. As a Google hosting service provider, we provide Google Cloud, Google Maps, Google Office Suite, and Google Cloud certification training services.

Cloud Ace  is a global strategic partner of Google Cloud. It has more than 300 engineers and is also the highest level partner of Google. It has won Google Cloud Partner Awards many times. As a Google hosting service provider, we provide Google Cloud , Google Maps , Google Office Suite , and Google Cloud certification training services .  

In December 2022, Google Cloud announced the general availability of AlloyDB for PostgreSQL, a fully managed, PostgreSQL-compatible database service that provides powerful options for modernizing legacy proprietary databases and scaling existing PostgreSQL workloads.

In early 2022, a preview release of AlloyDB for PostgreSQL migration was launched using Database Migration Service (DMS) .

Recently, Google Cloud announced the general availability of DMS for AlloyDB migrations from PostgreSQL sources.

 AlloyDB for PostgreSQL

When customers look to standardize on AlloyDB for PostgreSQL, they expect a smooth migration path. They needed a solution that was easy to set up and use without administrative overhead. Additionally, it should be able to move data accurately and securely with minimal disruption to applications. This is what database migration services provide.

AlloyDB for PostgreSQL offers a range of advantages that make it an attractive choice for the target database. It has better scalability, higher availability, and faster performance than open source PostgreSQL.

In performance tests, AlloyDB processes transactional workloads more than 4 times faster than standard PostgreSQL and delivers analytical queries 100 times faster than standard PostgreSQL. Since it is fully compatible with PostgreSQL, the technology can be leveraged seamlessly and easily.

While AlloyDB offered significant performance improvements over traditional PostgreSQL databases, it needed to meet the customer's migration requirements. DMS provides an easy-to-use migration solution with no administrative overhead. It also provides accurate, secure data transfer with minimal disruption to applications, making it a solid choice for organizations looking to transition to it as a standard database solution.

What we learned in the preview

Since launching DMS support for AlloyDB migrations, Google Cloud has helped businesses of all sizes improve database performance, scalability, and availability. Customers benefit from features such as index advisors and adaptive autovacuum, which reduce administrative overhead and improve performance.

Google Cloud is also helping customers achieve higher application availability by migrating to AlloyDB's highly scalable and elastic infrastructure. Full PostgreSQL compatibility and transparent pricing make it easy to take advantage of the technology.

DMS provides these customers with a fast, serverless, and secure migration path from PostgreSQL sources to AlloyDB for PostgreSQL, whether the source is an on-premises database, a self-managed database on Google Cloud, or a cloud database such as Amazon Aurora.

"Using DMS was really great, the configuration and setup was so easy and we were able to migrate our workloads with no downtime. Once we landed on AlloyDB, we were amazed at how seamless and flawless the experience was, it met all our requirements , including handling peak traffic." - Hiroaki Karasawa, Full-Stack Node.js Development and Cloud Native Infrastructure Manager, dinii inc.

“As a cloud-based SaaS ticketing platform, data continuity and system uptime are critical to our operations. We migrated from Amazon Aurora to Cloud SQL using DMS in 2021 and used it again in late 2022 to migrate to AlloyDB for PostgreSQL. Our primary concern is minimizing downtime, and that's where DMS proves its capabilities." "The beauty of DMS is its simplicity and reliability. The simple reality is that without Google's DMS, we still Knowing how to use Amazon Aurora and having performed two major database migrations in one year gives our team the agility to keep up with the latest and greatest cloud offerings that a provider like Google Cloud has to offer." - Oliver Morgan, CEO of Ventrata  

What's new in the GA release

The GA release offers enhanced security through Customer Managed Encryption Keys (CMEK), suitable for organizations with strict encryption policies. CMEK is now available for PostgreSQL to AlloyDB migrations, giving you greater control over the keys used to encrypt data at rest, ensuring the highest level of data protection during and after the migration.

Many Google Cloud services support CMEK. When you use CMEK to protect data in Google Cloud services, the CMEK keys are under your control.

Migrate to AlloyDB using Database Migration Service

Migration to AlloyDB is easy with DMS. First, navigate to the database migrations page in the Google Cloud console, create a new migration job, and follow these five easy steps:

  1. Choose the type of database you want to migrate, and see what you need to do to set up your source.

  2. Create a source connection profile, which contains information about the source database. The connection profile can be used later for other migrations. Here you can set up a Customer Managed Encryption Key (CMEK).

  3. Create an AlloyDB for PostgreSQL target cluster that suits your business needs.

  4. Define connection method: DMS provides a guided connection path to help you connect.

  5. Test your migration efforts and start when you're ready.

When a migration job starts, DMS takes an initial snapshot of the data, then replicates new changes as they occur. The migration job will continue to copy the source data until you decide to initiate the cutover. Once the cutover is initiated, replication stops and you can redirect your application to use a fresh AlloyDB cluster with all source data ready.

Guess you like

Origin blog.csdn.net/CLOUDACE/article/details/131460921