An enterprise cloud engineering team is evaluating Google Cloud database solutions and persistent block storage types for an infrastructure modernization project. Match each storage or database service on the left to the corresponding workload architecture requirement on the right.
- Cloud SpannerGlobally distributed relational database requiring strong ACID transactional consistency and SQL querying across multiple regions.
- Cloud BigtableHigh-throughput, low-latency NoSQL database optimized for heavy real-time analytical and time-series workloads.
- Persistent Disk Balanced (pd-balanced)Cost-effective general-purpose block storage backed by SSD performance for standard enterprise application boot and data disks.
- Local SSDEphemeral, non-persistent block storage physically attached to the Compute Engine host server for sub-millisecond scratch space.
Answer
Cloud Spanner matches globally distributed relational ACID requirements; Cloud Bigtable matches high-throughput NoSQL time-series workloads; Persistent Disk Balanced matches cost-effective SSD general-purpose block storage; Local SSD matches ephemeral physically attached scratch storage.
Each service aligns directly with its fundamental design characteristics: Cloud Spanner handles global relational transactions; Cloud Bigtable provides scalable NoSQL high-throughput storage; pd-balanced delivers cost-effective durable block storage; Local SSD supplies ultra-fast ephemeral host storage.
Step-by-Step Solution
Key Concept
Selecting GCP Managed Databases and Block Storage Options