What's changed: Created Professional Cloud Architect Chapter 6 (Domain 4 "Analyze and optimize": cost optimization and business alignment = billing/budget alerts (notify-only)/CUD/Spot/Active Assist/lifecycle/label allocation/KPI alignment; technical process optimization = SRE (SLI/SLO/error budget)/CI-CD (Cloud Build/Cloud Deploy)/deployment strategies (canary/blue-green/rollback)/incident response/postmortems).
6.2Optimizing technical processes (SRE, CI/CD, change management)
Understand site reliability engineering operations (SLIs/SLOs/error budgets), safe delivery via CI/CD with deployment strategies (canary, blue/green, rollback), incident response and postmortems, and optimizing cross-team collaboration and decision-making.
A great architecture delivers value only when run by great processes. Balance reliability and change velocity through SRE and CI/CD practices.
6.2.1SRE and reliability operations
Site reliability engineering (SRE) manages reliability with measurable targets: SLIs (metrics of user experience), their target SLOs, and the allowed deviation error budget. With budget remaining, ship changes aggressively; when nearly exhausted, throttle changes and prioritize stability. This quantifies the "velocity vs reliability" tradeoff. Map "user-facing target = SLO" and "allowed deviation = error budget."
6.2.2CI/CD and deployment strategies
Automate safe delivery with CI/CD (build/test in Cloud Build, release with Cloud Deploy). Risk-limiting deployment strategies include canary (release to a subset first), blue/green (switch between old/new environments), and rollback (revert quickly on issues). When incidents occur, limit impact via incident response, then prevent recurrence with a postmortem (blameless analysis). Map "gradual rollout = canary," "instant revert = rollback," and "prevent recurrence = postmortem."
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.