Diagram
A decision tree that branches on workload type: unstructured data leads to Cloud Storage, analytics to BigQuery, relational transactions to Cloud SQL or Spanner, and NoSQL operational data to Firestore or Bigtable, each with its common business use case.
Matching Business Scenarios to the Best-Fit Service
Matching business scenarios to the best-fit service depends on the primary workload and access pattern. Archiving needs cheap retention, transactions need relational correctness, real-time operations need low-latency scale, mobile apps need live sync, and reporting needs analysis over large data. Cost, performance, and functional fit together determine the choice.
| Business scenario | Best-fit service | Why it fits |
|---|---|---|
| Archiving | Cloud Storage | Low-cost object storage for files, backups, and long-term retention. |
| Ecommerce transactions | Cloud SQL or Cloud Spanner | Cloud SQL handles regional relational transactions; Cloud Spanner handles global, strongly consistent relational transactions. |
| Real-time analytics | BigQuery or Cloud Bigtable | BigQuery analyzes large datasets with SQL; Bigtable serves high-throughput, low-latency operational data. |
| Mobile application backend | Firestore | Document model with real-time sync and offline support for mobile and web clients. |
| Enterprise reporting | BigQuery or Cloud SQL | BigQuery supports large-scale analytical reporting; Cloud SQL supports reporting from operational relational data. |
Domain 2 of 6
27 practice questions
Practice this DomainLast updated