Google Associate Cloud EngineerDeploying and implementing a cloud solutionMedium
A company is migrating a large, monolithic Java application to Google Cloud. The application requires a traditional, highly relational database with strong ACID properties and high availability. The database size is expected to grow to several terabytes. The company wants a fully managed service to minimize operational overhead. Which Google Cloud database service is the best fit?
- ABigQuery
- BCloud Spanner
- CCloud SQL
- DCloud Firestore
Show answer & explanationAnswer & explanation
Correct answer: C. Cloud SQL
Cloud SQL is a fully managed relational database service that supports traditional databases like MySQL, PostgreSQL, and SQL Server, offering strong ACID properties and high availability suitable for monolithic applications up to several terabytes.
Why the other options are wrong
- A. BigQuery is a serverless data warehouse for analytics, not an operational relational database for a transactional application backend.
- B. Cloud Spanner is a globally distributed, horizontally scalable relational database, but it's overkill and more complex for a 'traditional, highly relational' monolithic application that might not need global distribution or horizontal scalability initially.
- D. Cloud Firestore is a NoSQL document database, unsuitable for 'highly relational' requirements.
Cloud SQL
A fully managed relational database service for MySQL, PostgreSQL, and SQL Server.
- Offers high availability, replication, and automatic backups.
- Supports traditional relational database schemas and SQL.
- Minimizes operational overhead for database management.
Memory trick: SQL for tradition, Spanner for global, Firestore for NoSQL.