A enterprise solution architect is designing the storage and database architecture for a multi-service cloud platform on Google Cloud. Match each technical application workload requirement on the left with the optimal Google Cloud database or storage service on the right that best satisfies the access pattern, consistency, and operational criteria.
- Global order processing system requiring multi-region ACID transactions, strong consistency, ANSI SQL support, and dynamic horizontal scaling without maintenance downtime.Cloud Spanner
- Ad-tech user profile feature store requiring single-digit millisecond latency for massive volume key-value writes and lookup scans by row key at high throughput.Cloud Bigtable
- Cross-platform client mobile app requiring rich document hierarchy querying, live listener notifications for state changes, and client SDK offline data synchronization.Firestore
- Centralized immutable telemetry ingest bucket storing raw unstructured blob objects with automated tier transitions based on object age for cost optimization.Cloud Storage
Cevap
Global order processing maps to Cloud Spanner; Ad-tech user feature store maps to Cloud Bigtable; Cross-platform client app maps to Firestore; Centralized immutable telemetry ingest bucket maps to Cloud Storage.
Each requirement strictly aligns with the core architecture parameters of the matching GCP product: Cloud Spanner for global multi-region relational ACID transactions, Cloud Bigtable for ultra-low latency key-value high-throughput operations, Firestore for real-time mobile document sync, and Cloud Storage for blob objects with lifecycle management policies.
Adım Adım Çözüm
Anahtar Kavram
Matching workload access patterns, consistency requirements, and scale demands to appropriate GCP database and storage products.