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).
The recommendations in the cost optimization pillar of the Well-Architected
Framework are aligned with the following core principles:
resources deliver measurable business value by aligning IT spending with
business objectives. Prioritize investments that directly contribute to
revenue, customer satisfaction, or operational efficiency. Grounding
document:
https://docs.cloud.google.com/architecture/framework/cost-optimization/align-cloud-spending-business-value
organization consider the cost impact of their decisions and activities.
Provide teams with the visibility and information they need to make informed,
cost-conscious choices. Grounding document:
https://docs.cloud.google.com/architecture/framework/cost-optimization/foster-culture-cost-awareness
pay only for what you consume. Select the most cost-effective resource types,
sizes, and locations that meet your technical and business requirements.
Grounding document:
https://docs.cloud.google.com/architecture/framework/cost-optimization/optimize-resource-usage
costs, and proactively make adjustments as needed to optimize your spending.
This iterative approach helps identify and address inefficiencies before they
become significant. Grounding document:
https://docs.cloud.google.com/architecture/framework/cost-optimization/optimize-continuously
The following are examples of Google Cloud products and features that are
relevant to cost optimization:
trends.
data using SQL and BI tools.
reports.
reaches predefined thresholds.
rightsizing opportunities, and unused commitments.
to help developers and application owners quickly identify their most
expensive, fluctuating, or underutilized cloud resources.
one dashboard.
cost spikes.
Run functions, and GKE Autopilot reduce operational overhead and pay-per-use
scaling.
Committed Use Discounts (CUDs) for stable workloads.
storage classes (Nearline, Coldline, Archive) based on age or access.
for cost attribution.
environment, team, or application.
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:
process?
departments?
testing, production)?
ongoing?
Use the following checklist to evaluate the architecture's alignment with
cost-optimization recommendations:
(e.g., env, team, app).
regular cost reviews.
and active alerts.
suggestions provided by Active Assist Recommender.
Use Discount coverage.
identified and removed monthly.
unless specific technical constraints exist.
buckets to minimize archival costs.