Google Cloud Well-Architected Framework skill for the Cost Optimization pillar
面向成本优化支柱的Google Cloud架构完善框架技能
Overview
概述
The Cost Optimization pillar of the Google Cloud Well-Architected Framework
provides a structured approach to optimize the costs of your cloud workloads
while maximizing business value. Cloud costs differ significantly from
on-premises capital expenditure (CapEx) models, requiring a shift to operational
expenditure (OpEx) management and a culture of accountability (FinOps).
Google Cloud架构完善框架的成本优化支柱提供了一种结构化方法,可在最大化业务价值的同时优化云工作负载的成本。云成本与本地资本支出(CapEx)模式存在显著差异,这要求转向运营支出(OpEx)管理以及问责文化(FinOps)。
Core principles
核心原则
The recommendations in the cost optimization pillar of the Well-Architected
Framework are aligned with the following core principles:
The following are examples of Google Cloud products and features that are
relevant to cost optimization:
Visibility and monitoring:
Cloud Billing reports: Native dashboards for visualizing spending and
trends.
BigQuery billing export: Enables granular, custom analysis of billing
data using SQL and BI tools.
Looker Studio: Used for creating detailed, shared cost dashboards and
reports.
Billing alerts and budgets: Automated notifications when spending
reaches predefined thresholds.
Automation and optimization tools:
Recommender / Active Assist: Automatically identifies idle resources,
rightsizing opportunities, and unused commitments.
Cloud Hub Optimization: Integrates billing and resource utilization data
to help developers and application owners quickly identify their most
expensive, fluctuating, or underutilized cloud resources.
FinOps hub: Presents active savings and optimization opportunities in
one dashboard.
Billing quotas: Limits on resource consumption to prevent unexpected
cost spikes.
Efficient infrastructure:
Managed services and serverless services: Services like Cloud Run, Cloud
Run functions, and GKE Autopilot reduce operational overhead and pay-per-use
scaling.
Compute Engine: Use of Spot VMs for fault-tolerant workloads and
Committed Use Discounts (CUDs) for stable workloads.
Cloud Storage Lifecycle Policies: Automatically moves data to lower-cost
storage classes (Nearline, Coldline, Archive) based on age or access.
Organization and governance:
Resource Manager: Logical structure (Organizations, Folders, Projects)
for cost attribution.
Labels: Metadata tags for categorizing and filtering costs by
environment, team, or application.
Organization Policy Service: Enforces constraints (e.g., restricted
regions or machine types) to control costs.
Ask appropriate questions to understand the cost-related requirements and
constraints of the workload and the user's organization. Choose questions from
the following list:
How do you incorporate cost considerations into your cloud architecture design
process?
How do you foster a culture of cost awareness among your development teams?
How do you monitor and manage cloud costs across different projects or
departments?
What strategies do you use to optimize the cost of your compute resources?
How do you balance cost optimization with the need for agility and innovation?
How do you ensure that you are not over-provisioning cloud resources?
How do you use data and analytics to drive cost optimization decisions?
How do you optimize costs in different environments (e.g., development,
testing, production)?
How do you ensure that your cost optimization efforts are sustainable and
ongoing?
How do you measure the success of your cloud cost optimization initiatives?
提出合适的问题,以了解工作负载和用户组织的成本相关需求与约束。可从以下列表中选择问题:
您如何将成本考量融入云架构设计流程?
您如何在开发团队中培养成本意识文化?
您如何跨不同项目或部门监控和管理云成本?
您采用哪些策略优化计算资源的成本?
您如何平衡成本优化与敏捷性和创新需求?
您如何确保不过度配置云资源?
您如何利用数据和分析驱动成本优化决策?
您如何在不同环境(如开发、测试、生产)中优化成本?
您如何确保成本优化工作可持续且持续进行?
您如何衡量云成本优化举措的成功?
Validation checklist
验证清单
Use the following checklist to evaluate the architecture's alignment with
cost-optimization recommendations:
Cost Attribution: 100% of resources are labeled with key metadata
(e.g.,
env
,
team
,
app
).
Granular Visibility: BigQuery billing export is enabled and used for
regular cost reviews.
Budgets and Alerts: Every project or business unit has defined budgets
and active alerts.
Rightsizing: Resources are regularly adjusted based on rightsizing
suggestions provided by Active Assist Recommender.
Commitment Strategy: Spend is reviewed monthly to optimize Committed
Use Discount coverage.
Idle Resource Management: Unused disks, IP addresses, and idle VMs are
identified and removed monthly.
Managed Services: Serverless options are preferred for new workloads
unless specific technical constraints exist.
Storage Tiers: Lifecycle policies are active for all major storage
buckets to minimize archival costs.