Diagram
A decision tree branching on data shape and workload to choose Cloud Storage for objects, BigQuery for analytics, Cloud SQL for regional transactions, or Spanner for global transactions.
Choosing by Structure and Workload
Choosing by structure and workload means matching data shape and access pattern to the right core service. The four core services differ in structure, scale, and whether they fit operational or analytical use, so the choice of storage strategy depends on what the data looks like and how it will be queried:
| Service | Data structure | Scales to | Choose when |
|---|---|---|---|
| Cloud Storage | Objects in buckets with IDs and metadata | Virtually unlimited objects, with cross-region replication | The data is unstructured files, media, backups, archives, or static web assets |
| BigQuery | Columnar analytical tables in datasets | Petabyte-scale analytics with decoupled storage and compute | The work is analytical queries, reporting, and ML over large datasets |
| Cloud SQL | Relational tables for MySQL, PostgreSQL, or SQL Server | Regional transactional workloads | The work is operational transactions with a specific relational engine |
| Spanner | Relational tables for global applications | Mission-critical global scale | The work is operational transactions that must grow and stay available globally |
Domain 1 of 6
26 practice questions
Practice this DomainLast updated