A financial services firm is migrating a custom relational PostgreSQL database to a Compute Engine virtual machine. The workload requires steady, reliable IOPS and low latency for transactional processing, but the engineering team wants a cost-effective block storage option that performs better than standard HDDs without paying the premium cost of high-performance SSDs. Additionally, the data must persist independently of the VM lifecycle and support automated snapshot backups. Which storage option best satisfies these requirements?
- Balanced Persistent Disk (pd-balanced)Answer
- BLocal SSD
- CCloud Bigtable
- DCloud Storage Coldline bucket mounted as a file system
Answer
Balanced Persistent Disk (pd-balanced) is the recommended GCP block storage solution for general enterprise workloads needing SSD performance at a lower cost point while retaining persistence and snapshot support.
Balanced Persistent Disk (pd-balanced) provides backed SSD storage optimized for enterprise applications that need a balance of performance and cost. It supports snapshots, persistent attach/detach capabilities, and reliable IOPS required by relational database engines like PostgreSQL on Compute Engine.
Step-by-Step Solution
Key Concept
Selecting persistent block storage types for Compute Engine database workloads based on IOPS performance, persistence, and cost constraints.
Estimated Time:1m 30s