A cloud architecture team is designing the infrastructure for a newly onboarded suite of enterprise applications. Match each technical workload requirement to the most appropriate Google Cloud storage or database option based on Google-recommended practices.
- A mobile application backend requiring real-time document synchronization across offline devices, client SDK integration, and seamless serverless scaling.Firestore
- A mission-critical relational database requiring global multi-region ACID compliance, horizontal scaling without sharding, and up to 99.999% availability.Cloud Spanner
- A high-performance database running on Compute Engine virtual machines requiring provisioned performance up to 120,000 IOPS independent of storage volume capacity.Extreme Persistent Disk (pd-extreme)
- A large-scale IoT sensor data processing pipeline requiring low single-digit millisecond latency for massive throughput of unstructured time-series records.Cloud Bigtable
Cevap
Matching pairs: Mobile app offline sync matches Firestore; Global multi-region relational ACID matches Cloud Spanner; Compute Engine VM requiring independent high IOPS provisioning matches Extreme Persistent Disk (pd-extreme); Large-scale IoT time-series processing matches Cloud Bigtable.
Matching each workload to its ideal GCP storage option respects core database engine capabilities and persistent disk performance characteristics: Firestore handles mobile document state sync; Cloud Spanner handles global relational scale; Extreme Persistent Disk allows independent IOPS provisioning for VM workloads; Cloud Bigtable handles massive IoT time-series data ingestion.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Database and Block Storage Solutions Based on Workload Characteristics