A global telecommunications enterprise is migrating its legacy billing and subscription management platform from an on-premises data center to Google Cloud. The architecture consists of a 12 TB single-region PostgreSQL relational database with historical technical debt and a set of simple, stateless HTTP web services that process customer subscription requests.
The organization mandates a phased migration strategy with zero data loss and minimal operational maintenance after migration. The existing on-premises network link is a low-bandwidth Cloud VPN connection that cannot sustain continuous database replication alongside daily production traffic.
Which combination of Google Cloud services and migration patterns best addresses the technical debt, network bandwidth constraints, and operational goals?
- Provision a Dedicated Interconnect connection, use Database Migration Service (DMS) for continuous Change Data Capture (CDC) to Cloud SQL for PostgreSQL, and deploy the stateless HTTP microservices to Cloud Run.Cevap
- BMigrate the on-premises database to Cloud Spanner using custom data export scripts, and host the stateless HTTP microservices on a multi-zone Google Kubernetes Engine (GKE) Enterprise cluster.
- COrder a Google Cloud Transfer Appliance to physically import the 12 TB database backup, and deploy the stateless HTTP microservices to Google Kubernetes Engine (GKE) using Autopilot mode.
- DEstablish a Dedicated Interconnect, migrate the PostgreSQL database to Cloud SQL using Database Migration Service (DMS), and configure HA VPN over Dedicated Interconnect while granting primitive Editor roles to the application service account to simplify network resource provisioning.