01
Cloud Compute
Renting the machine: matching instance families' resource ratio to the workload and sizing, the startup time and freshness balance of the machine image and startup script, the cost and interruption risk of persistent against interruptible capacity, launch templates for a repeatable instance definition, the combined behavior of scaling policies and health checks, and cluster and task-based managed container services.
- 01 Virtual Machine Instances Four workload profiles are mapped to three instance families, and each match counts the idle processor, idle memory, and the size at which the bottleneck appears; the same demand is split across six different instance sizes, measuring how fixed overhead and failure exposure move in opposite directions; on a single instance, which decisions stay with you, which cannot be undone, and how many fleet hours a correction takes are worked out.
- 02 Machine Images Eight items done at startup are embedded into the image one at a time, and the seconds each item gains are counted alongside the staleness it costs; the embedding level is scanned from zero to eight, working out startup duration, external call count, dependency type, monthly bake load, and stale item-days; which dependency the work remaining at startup is bound to, and whether startup stops when that dependency drops, are measured.
- 03 Persistent and Interruptible Capacity Four job types are run on interruptible capacity, and interruption notice is scanned from zero to three hundred seconds to count the work lost at each type; over a thirty-day period, interruption count, lost job-hours, restart load, and completion rate are worked out; the job type that does not tolerate interruption at all is named, and the mix of persistent with interruptible is scanned.
- 04 Launch Templates Manually launched instances and template-launched ones are compared field by field at the end of a period, and drifted instances and separate configuration variants are counted; when the template is updated, instances left behind, the number of versions running at the same time, and instances a security patch has not reached are worked out; the template's own input surface and the fields that cannot be undone are named.
- 05 Auto Scaling Groups The scaling policy and health checks are run together in the same group, and group-size swing, the number of instances changed at once, and the rounds spent below capacity are counted; the health check threshold and the scaling cooldown duration are scanned as nine pairs, and the pair that produces constant change is named; the daily cost of constant change and the group's three items that cannot be undone are worked out.
- 06 Managed Container Services The same workload is counted through fifteen decision items across three execution levels — self-run cluster, managed cluster, and task-based execution — and how many decisions stay with you, how many are handed off, and what the annual maintenance load is at each level are worked out; each level's items that cannot be undone are named, and the configuration that does not travel at exit along with the handoff's payback period are measured.