A media publishing enterprise is migrating its legacy digital asset archiving platform from an on-premises data center to Google Cloud. The existing architecture consists of a stateless Java HTTP API service that processes metadata requests and an 8 TB on-premises MySQL relational database. The workload must remain operational throughout a 30-day migration window.
The enterprise wants to eliminate infrastructure management overhead, adopt managed cloud services, and ensure zero-downtime database schema updates during migration. Which TWO architecture and migration strategies should you recommend?
- Containerize the stateless Java API service and deploy it to Cloud Run to handle incoming metadata requests.Cevap
- Use Database Migration Service (DMS) for continuous replication from on-premises MySQL to Cloud SQL, and apply an expand-contract pattern for schema updates.Cevap
- CDeploy the stateless Java API service onto a dedicated Google Kubernetes Engine (GKE) cluster with custom node pools.
- DMigrate the 8 TB relational database directly to Cloud Spanner to ensure multi-region global horizontal scaling.
Cevap
The optimal solution is to containerize the stateless API for deployment on Cloud Run and use Database Migration Service (DMS) with Cloud SQL alongside an expand-contract database schema pattern.
Deploying the containerized stateless service to Cloud Run eliminates server and cluster maintenance debt while providing automatic scaling. Pairwise, using Database Migration Service (DMS) with Cloud SQL enables continuous data synchronization from the on-premises MySQL instance, while the expand-contract pattern ensures backward-compatible schema changes without application downtime.
Adım Adım Çözüm
Anahtar Kavram
Legacy cloud migration strategies balancing compute serverless replatforming and database continuous replication.
Tahmini Süre:2m 0s