Cloud cost
Buying for the peak leaves half the capacity idle
CapEx buys for the peak and leaves 51% idle. OpEx pays for what is used. TCO compares them.
The last section is about running in the cloud: cost first, then reliability. Here is what one application needs across a year. It is quiet for months, then peaks in December. In your own datacentre you must buy for that peak, up front. That is capital expenditure. Over the year, 51 percent of what you bought sits idle. In the cloud you pay only for the bars: operating expenditure, month by month. To compare the two fairly, use total cost of ownership, which counts everything.
Cloud cost · Going deeper
What TCO counts
TCO adds hardware, space, power, staff and idle capacity to the comparison.
Resource hierarchy
One tree, and rules flow down it
Organization, folders, projects, resources: a policy set above is inherited below.
Variable cost needs structure, and Google Cloud gives every customer one tree. At the top is the organization node: the whole company. Under it are folders, usually one for each department or team. Folders hold projects. A project is the unit for billing and permissions. And projects hold resources: the databases, virtual machines and buckets you actually use. Now grant a role on the Engineering folder. Every project and resource beneath it inherits that role. Finance is untouched.
Resource hierarchy · Going deeper
Levels and benefits
Access control, inheritance, compliance and visibility.
Check yourself
A role is granted on folder B. Which projects does it apply to?
Consumption controls
A budget warns you. It does not stop the spending
Budget alerts warn at thresholds, quotas cap usage, and Cloud Billing reports show where money went.
Now the controls. Here is one month of spending against a budget of three thousand dollars. The line is the total so far. On day eleven, someone leaves a job running, and the line steepens. The budget has three threshold rules, at fifty, ninety and one hundred percent. Each sends an alert as the line crosses it: on days 16, 25 and 27. But look past one hundred percent. The line keeps rising. A budget warns. To actually limit usage, you set a quota.
Consumption controls · Going deeper · 1 of 2
Five consumption controls
Reports show, budgets warn, quotas cap, Spot VMs save, the scheduler schedules.
Consumption controls · Going deeper · 2 of 2
Financial governance
People, process and technology, with a named owner for every cost.
Reliability
A measurement, a target and a promise
The SLI is measured, the SLO is the internal target, and the SLA is the promise to customers.
Reliability is managed with three numbers on the same scale. The service level indicator is what you measured. This month the service was available ninety-nine point nine five percent of the time. The service level objective is the target the team sets itself: ninety-nine point nine. The service level agreement is the promise made to customers: ninety-nine point five, with compensation if it is missed. The target is tighter than the promise, on purpose. Missing the target is a warning. Missing the promise costs money.
Reliability · Going deeper
Downtime, and designing for it
Redundancy, replication, scalable infrastructure and backups.
Check yourself
What has happened this month?
Observability
Five products, each answering one question
Monitoring, Logging, Trace, Profiler and Error Reporting, watching the four signals.
To hit those targets you have to see what the service is doing. Say checkout is slow for some customers. Cloud Monitoring answers: is something wrong? It holds the metrics and sends the alerts. Cloud Logging answers: what happened? Cloud Trace follows one request across every service, and shows where the delay is. Cloud Profiler shows which code is using the processor and memory. Error Reporting gathers the failures and groups them. And on any service, four signals are worth watching: latency, traffic, saturation and errors.
Observability · Going deeper · 1 of 2
Operations terms
Reliability, high availability and the four signals.
Observability · Going deeper · 2 of 2
Clue words for cost and operations
The smallest section: 10% of the exam.
Check yourself
A team describes a problem as shown. Which product answers it?
Lesson complete
You finished “Controlling cost and running reliably”
Answer the questions along the way to see your score here.