Professional Cloud ArchitectAnalyze and optimize technical and business processesHard
A large manufacturing company is migrating its legacy ERP system to Google Cloud. The ERP system relies on a complex, highly customized database schema that has evolved over 20 years. The company's database administrators are highly skilled in Oracle Database management but have limited experience with cloud-native databases. The migration strategy prioritizes minimal application code changes and maximum compatibility with existing SQL queries and stored procedures. Which Google Cloud database service should they choose to minimize migration effort and leverage existing DBA skills?
- AFirestore in Datastore mode.
- BCloud Spanner.
- CBare Metal Solution for Oracle.
- DCloud SQL for PostgreSQL.
Show answer & explanationAnswer & explanation
Correct answer: C. Bare Metal Solution for Oracle.
Bare Metal Solution for Oracle allows running Oracle Database directly on Google Cloud's infrastructure, providing full control and compatibility with existing Oracle licenses, tools, and DBA skills. This minimizes application code changes and leverages the highly customized schema without modification, addressing all key requirements.
Why the other options are wrong
- A. Firestore in Datastore mode is a NoSQL document database, completely incompatible with a relational Oracle schema and existing SQL queries/stored procedures.
- B. Cloud Spanner is a globally distributed, strongly consistent relational database, but migrating a complex Oracle schema to Spanner would require significant schema and application code changes due to its different SQL dialect and architectural paradigm.
- D. Cloud SQL for PostgreSQL is a managed relational database, but migrating from Oracle to PostgreSQL would still involve schema conversion, SQL dialect changes, and potential stored procedure rewrites, requiring significant effort and new DBA skills.
Google Cloud Database Migration Strategies
Google Cloud offers various database services and migration paths, each with different levels of compatibility, effort, and cloud-nativeness, depending on the source database and application requirements.
- Lift-and-shift: Minimal changes, often using Bare Metal Solution or Compute Engine.
- Re-platform: Migrate to a managed service (e.g., Cloud SQL), some schema/code changes.
- Re-architect: Migrate to a cloud-native database (e.g., Spanner, Firestore), significant changes.
Memory trick: Oracle's old, cloud's new, Bare Metal makes it simple too!