Cloud Architecture Framework:
Optimize cost: Storage: Cost-optimization controls for Cloud Storage, Persistent Disk, and Filestore
Cloud Storage - Cloud Storage is a managed service for storing unstructured data. Store any amount of data and retrieve it as often as you like. GCS is one of the cheapest cloud resources for storing data files. The price depends on the storage location (Multi-regions, Dual-regions, and Regions) and class
Classes:
- Standard storage - Data that’s accessed frequently
- Nearline storage - Low-cost storage for infrequently accessed data that can be stored for at least 30 days*
- Coldline storage - Infrequently accessed data that can be stored for at least 90 days*
- Archive storage - Lowest-cost storage for infrequently accessed data that can be stored for at least 365 days*
* - You can delete, replace, or move an object before it has been stored for the minimum duration, but at the time you delete, replace, or move the object, you are charged as if the object was stored for the minimum duration.
Price components:
- Price of stored data (Gb) - The price of stored data starts from 20$ per Tb per month and is approximately twice cheaper for each next class, but operations are more expensive, classes (other than standard) have Minimum storage duration and Retrieval fees
- Operation charges - Operation charges apply when you perform operations within Cloud Storage. An operation is an action that makes changes to or retrieves information about resources such as buckets and objects in Cloud Storage. Where important forecast number of your operation, and not use other than Standard class for frequent accessed (read/write/meta) data
- Retrieval fees - A retrieval fee applies when you read, copy, move, or rewrite object data or metadata that is stored using Nearline storage, Coldline storage, or Archive storage
- Inter-region replication - Where applicable, inter-region replication is billed on a per-GB written basis.
- Autoclass Management fee - Buckets that have Autoclass enabled incur a monthly fee of $0.0025 for every 1000 objects stored within them
- Network egress within Google Cloud — Can be free or not depending on your destination
- Monitoring and Last modification — can help you find old not needed buckets without Lifecycle policies
- Lifecycle policies — can help you move old objects to cold tires and delete them after a selected period
Persistent Disk - Every VM instance that you deploy in Compute Engine has a minimum of one disk.
- For all persistent disks, you pay 24/7 - not important do you use the disk or not, include unattached disks — you will pay full price
- Disk speed depends on disk type and size - check the performance characteristics needed for your application, some time will be more price effective to use a big, but less fast (PD or Balanced) disk than SSD or Extreme
- Don’t use the persistent disk as a long-term backup - If you want to save your disk as a backup — make a snapshot (in the needed zone) or better an image (snap has some network price for data update)
- Delete a VM or GKE volume - not warranty PD will be deleted with the server or GKE PVC, regularly check your projects and recommendation system and delete lost disks.
- Snapshot Schedules - help you delete your old snapshot regularly
- Use regional persistent disks - only when protecting data against zonal outages is essential. Regional persistent disks are replicated to another zone within the region, so you incur double the cost of equivalent zonal disks.
Filestore - Filestore instances are fully managed file servers on Google Cloud that can be connected to Compute Engine VMs, GKE clusters, and your on-premises machines.
- The cost of a Filestore instance depends on its service tier, the provisioned capacity, and the region where the instance is provisioned.
- Select a service tier and storage type (HDD or SSD) that’s appropriate for your storage needs.
- Choosing the region and zone of a Filestore instance. You’re billed for egress traffic from the zone of the Filestore instance.
- Scale down the allocated capacity for Filestore instances that have low usage. You can scale down the capacity of instances in the High Scale SSD tier and Enterprise tier.
