Link copied to clipboard!

Group 5: Object & File Storage

Persistent storage services: Cloud Storage (object storage with multiple classes), Filestore (managed NFS), Persistent Disk (block storage), Local SSD (high-performance local), Archive Storage (long-term retention). Choose based on access patterns, performance requirements, and cost optimization needs.

Storage Hierarchy: Cloud Storage for objects and analytics; Filestore for POSIX file systems; Persistent Disk for VM storage; Local SSD for maximum performance; Archive Storage for long-term retention. Match storage class to access frequency.

Services & Core Identity

Cloud Storage

Object storage with multiple classes (Standard, Nearline, Coldline, Archive) for different access patterns and cost optimization.

Filestore

Fully managed NFS file system for applications requiring shared file storage with POSIX compliance.

Persistent Disk

Block storage for Compute Engine VMs with options for Standard (HDD) and SSD performance tiers.

Local SSD

High-performance local storage directly attached to VM instances for maximum throughput and lowest latency.

Archive Storage

Lowest-cost storage class for long-term archival with retrieval times measured in hours.

Key Differences

Dimension	Cloud Storage	Filestore	Persistent Disk	Local SSD	Archive Storage
Storage Type	Object	File (NFS)	Block	Block (local)	Object (cold)
Access Method	REST API/gsutil	POSIX file system	OS file system	OS file system	REST API (delayed)
Performance	High throughput	NFS performance	Consistent IOPS	Maximum IOPS	Archival only
Durability	99.999999999%	99.99%	99.999%	VM dependent	99.999999999%
Use Cases	Backup, analytics, CDN	Shared app data	VM boot/data disks	Cache, temp data	Compliance, backup
Cost Model	Storage + operations	Provisioned capacity	Provisioned size	Included with VM	Lowest storage cost

Mathematical Selection Model

Criteria [0..10]. Higher scores indicate better storage fit.

Object Storage Need File System Need High Performance Cost Sensitivity Archival Requirements Shared Access Analytics Workload Backup & Recovery

Score_CloudStorage = 0.30*C_objectStorageNeed + 0.25*C_analyticsWorkload + 0.20*C_backupRecovery + 0.15*C_costSensitivity + 0.10*C_scalability Score_Filestore = 0.35*C_fileSystemNeed + 0.25*C_sharedAccess + 0.20*C_posixCompliance + 0.15*C_legacyApps + 0.05*(10 - C_costSensitivity) Score_PersistentDisk = 0.30*C_vmStorage + 0.25*C_reliability + 0.20*C_performance + 0.15*C_snapshotNeed + 0.10*C_resizability Score_LocalSSD = 0.40*C_highPerformance + 0.25*C_lowLatency + 0.20*C_temporaryData + 0.10*C_cacheWorkload + 0.05*(10 - C_costSensitivity) Score_ArchiveStorage = 0.40*C_archivalRequirements + 0.30*C_costSensitivity + 0.20*C_complianceRetention + 0.10*(10 - C_accessFrequency)

{{s.name}}: {{s.val | number:2}}

Interpretation Rules

Cloud Storage: Backup/restore, data lakes, content distribution, analytics data, application assets
Filestore: Content management, shared application data, legacy file-based applications
Persistent Disk: VM boot disks, database storage, application data requiring consistent performance
Local SSD: Database caches, temporary processing, high-performance computing workloads
Archive Storage: Long-term backup, compliance archiving, disaster recovery, audit logs

When NOT to Use These Storage Options

Frequently accessed data in Archive Storage (use Standard Cloud Storage)
Database primary storage on Local SSD (risk of data loss)
Object storage needs with Filestore (use Cloud Storage)
Cross-platform file sharing with Persistent Disk (use Filestore)

Summary

GCP storage services provide comprehensive options from high-performance local storage to cost-optimized archival. Cloud Storage dominates for object storage and analytics, Filestore enables shared file systems, Persistent Disk provides reliable VM storage, Local SSD maximizes performance, and Archive Storage minimizes long-term costs. Choose based on access patterns, performance requirements, and cost constraints.

Scan with Phone