Match each Google Cloud database or persistent block storage service on the left with the workload architecture requirement on the right that it best satisfies.
- Cloud SpannerA fully managed relational database requiring horizontal scaling and global multi-region ACID transaction consistency.
- Cloud BigtableA high-throughput, low-latency NoSQL database optimized for petabyte-scale analytics and continuous time-series data.
- Cloud SQLA fully managed relational engine supporting standard PostgreSQL or MySQL with built-in regional high availability failover.
- Extreme Persistent Disk (pd-extreme)High-performance provisioned block storage attached to Compute Engine instances for IOPS-intensive applications like SAP HANA.
Cevap
Cloud Spanner pairs with global multi-region relational ACID requirements; Cloud Bigtable pairs with high-throughput NoSQL time-series data; Cloud SQL pairs with managed regional relational SQL engines; Extreme Persistent Disk pairs with provisioned high-IOPS block storage for Compute Engine.
Each Google Cloud storage and database technology fulfills specific operational and architectural constraints: Cloud Spanner supports global multi-region relational consistency with horizontal scaling; Cloud Bigtable provides high-throughput NoSQL capabilities for heavy time-series analytics; Cloud SQL provides standard managed relational databases with regional high availability; and Extreme Persistent Disk (pd-extreme) supplies high-provisioned IOPS block storage directly to Compute Engine VMs.
Adım Adım Çözüm
Anahtar Kavram
Planning GCP Database and Persistent Disk Types for Architectural Requirements