A digital media startup needs to host a stateless HTTP microservice that receives occasional web traffic throughout the day and store static thumbnail images that are rarely accessed after 30 days. Which TWO architectural decisions should you recommend to minimize operational and baseline compute costs while satisfying these business requirements?
- Deploy the stateless HTTP microservice on Cloud Run to automatically scale compute instances to zero when idle.Cevap
- Store static thumbnail images in Cloud Storage and use Object Lifecycle Management to transition objects to Nearline storage after 30 days.Cevap
- CDeploy the stateless HTTP microservice on a multi-zone Google Kubernetes Engine (GKE) Standard cluster with a fixed node count.
- DStore static thumbnail images in Cloud Spanner to maintain global transactional consistency for binary file storage.
Cevap
The optimal architectural choices to minimize costs are deploying the stateless HTTP microservice on Cloud Run to allow scaling to zero during idle periods, and storing static thumbnail images in Cloud Storage with Object Lifecycle Management to transition aging objects to lower-cost Nearline storage.
Deploying the microservice to Cloud Run eliminates compute costs when traffic is absent by scaling to zero instances. Storing media assets in Cloud Storage with Object Lifecycle Management ensures unstructured blobs are stored in the most economical storage tier based on access frequency.
Adım Adım Çözüm
Anahtar Kavram
Serverless compute right-sizing and object storage lifecycle optimization