A digital publishing platform is planning its Google Compute Engine infrastructure for two distinct backend services:
1. A high-throughput, in-memory caching tier that requires high memory-to-vCPU ratios, operating 24/7 with a 99.99% uptime requirement.
2. A batch image-resizing pipeline that processes asynchronous worker queues, where individual instance preemptions can be retried automatically without data loss.
Which machine configuration and pricing strategy should the cloud engineer select to optimize compute costs while satisfying the SLA requirements?
- Provision high-memory machine family instances backed by Committed Use Discounts for the caching tier, and provision Spot VMs for the batch image-resizing pipeline.Cevap
- BProvision Spot VMs for the in-memory caching tier to maximize hourly cost savings, and purchase 1-year Committed Use Discounts on standard machine types for the batch image-resizing pipeline.
- CMigrate the stateful in-memory caching tier to GKE Autopilot clusters to eliminate node-level management, assuming node memory state is preserved when Autopilot scales nodes to zero.
- DUse standard machine types for both workloads and rely exclusively on automatic Sustained Use Discounts without leveraging Spot VMs or Committed Use Discounts.
Cevap
Provision high-memory machine family instances backed by Committed Use Discounts for the caching tier, and provision Spot VMs for the batch image-resizing pipeline.
The correct strategy combines high-memory machine types with Committed Use Discounts for the 24/7 stateful caching service to guarantee availability and lower baseline costs, while leveraging Spot VMs for the fault-tolerant batch processing pipeline to maximize cost savings on interruptible tasks.
Adım Adım Çözüm
Anahtar Kavram
Compute Engine Machine Type Selection & Discount Models (CUD vs. Spot VMs)