You currently have transactional data stored on-premises in a PostgreSQL database. To modernize your data environment, you want to run transactional workloads and support analytics needs with a single database. You need to move to Google Cloud without changing database management systems, and minimize cost and complexity. What should you do?
To modernize your data environment while keeping the same database management system and minimizing cost and complexity, the best option is to migrate your PostgreSQL database to Cloud SQL for PostgreSQL. Cloud SQL is a fully managed service that handles maintenance, backups, and updates, which aligns with minimizing complexity. Additionally, since Cloud SQL directly supports PostgreSQL, it avoids the need to change database systems, thereby minimizing additional costs associated with migrating and training on a new system. This option supports both transactional workloads and analytics through federated queries, making it an optimal choice.
- AlloyDB is a fully managed, PostgreSQL-compatible database service with industry-leading performance.
Why not D
AlloyDB for PostgreSQL is a fully managed, PostgreSQL-compatible database service that's designed for your most demanding workloads, including hybrid transactional and analytical processing. ref: https://cloud.google.com/alloydb/docs/overview
https://cloud.google.com/alloydb#all-features The requirement is to minimize cost and complexity. Cloud SQL would be the best choice.
Considering the cost factor, I'll go with D. If "minimize cost" is not present in the question, then I'd go with 'B' AlloyDB. Cloud SQL for PostgreSQL: Generally less expensive than AlloyDB. AlloyDB: Can be significantly more expensive due to its advanced features and high performance capabilities.
minimize cost and complexity
They currently have transactional data stored on-premises in a PostgreSQL database and they want to modernize their database that supports transactional workloads and analytics .If they select cloud Sql (postgreSQL) it will minimize the cost and complexity. and for analytics purpose they can create federated queries over cloudSql(postgreSql) https://cloud.google.com/bigquery/docs/federated-queries-intro This approach will minimze the cost
B. Migrate your workloads to AlloyDB for PostgreSQL.
Database Migration Service makes it easier for you to migrate your data to Google Cloud. This service helps you lift and shift your PostgreSQL workloads into Cloud SQL.
B - minimize cost Cloud SQL for PostgreSQL: Generally less expensive than AlloyDB, especially for smaller deployments. AlloyDB: Can be significantly more expensive due to its advanced features and high performance capabilities.
so answer D?
B. Migrate your workloads to AlloyDB for PostgreSQL.
Sorry its D. Migrate your PostgreSQL database to Cloud SQL for PostgreSQL.
AlloyDB is for large scale and more expensive. We want to minimize cost and complexity, so the answer is D.
It's a little complicated, considering it says minimize costs (Cloud SQL) and run transactional workloads and support analytics needs (AlloyDB). I consider B. because you can minimize costs in the long-term instead of doing it immediately with possible extra costs in the long-term. Think about it
Minimize cost. https://cloud.google.com/alloydb?hl=en AlloyDB offers superior performance, 4x faster than standard PostgreSQL for transactional workloads. That does not come without cost.
AlloyDB
Because AlloyDB is optimised for hybrid transactional and analytical processing (HTAP), meaning you can run both transactional workloads and analytics on the same database with excellent performance.