Professional Cloud ArchitectManage and provision solution infrastructureMedium
A large e-commerce company is migrating its monolithic on-premises application to a microservices architecture on Google Kubernetes Engine (GKE). They need a persistent storage solution for their databases and stateful services that can be accessed by multiple pods concurrently, with high performance and low latency. The storage should also be highly available and support automatic failover within the GKE cluster. Which Google Cloud storage solution should they choose?
- AFilestore High Scale instances
- BCloud SQL instances
- CCloud Storage buckets
- DPersistent Disk with ReadOnlyMany access mode
Show answer & explanationAnswer & explanation
Correct answer: A. Filestore High Scale instances
Filestore High Scale instances provide high-performance, low-latency, and highly available NFS storage that can be mounted by multiple GKE pods concurrently, making it ideal for shared persistent storage for stateful microservices.
Why the other options are wrong
- B. Cloud SQL is a managed relational database service, not a general-purpose file storage solution for GKE pods.
- C. Cloud Storage is object storage and does not provide file system semantics required for concurrent mounting by multiple pods.
- D. Persistent Disk ReadOnlyMany allows multiple instances to read the same disk, but not write concurrently, which is needed for databases and stateful services.
Cloud Filestore High Scale
A fully managed, high-performance file storage service on Google Cloud, optimized for demanding workloads requiring shared file systems.
- Offers NFSv3 and NFSv4.1 protocol support.
- Provides high throughput and low latency.
- Suitable for GKE stateful applications requiring shared file systems.
Memory trick: GKE needs shared files, fast and ready.