An e-commerce platform processes user-uploaded product images using a stateless containerized microservice upon each upload. Media ingestion traffic is highly bursty during flash sales and drops to zero overnight. Additionally, images older than 30 days are accessed rarely but must remain accessible for regulatory auditing. The business objective is to minimize baseline infrastructure costs and operational overhead while satisfying all functional needs. Which TWO architectural choices should you recommend to achieve these goals?
- Deploy the stateless containerized image processing microservice on Cloud Run so that compute resources automatically scale up during traffic bursts and scale down to zero when idle.Cevap
- Implement Object Lifecycle Management on the Cloud Storage bucket to automatically transition images older than 30 days from Standard to Nearline or Coldline storage classes.Cevap
- CDeploy the image processing microservice to a Google Kubernetes Engine (GKE) cluster with dedicated node pools reserved via 3-year Committed Use Discounts.
- DStore user-uploaded image files directly as binary BLOB fields inside a multi-region Cloud Spanner database instance.
Cevap
Deploying the stateless container microservice on Cloud Run allows scaling down to zero during idle periods to eliminate baseline compute costs. Configuring Cloud Storage Object Lifecycle Management automatically moves images older than 30 days to lower-cost storage tiers, reducing long-term storage expenses.
Combining Cloud Run for container execution with Cloud Storage Object Lifecycle Management fulfills all functional and business goals. Cloud Run scales seamlessly to zero instances overnight to eliminate idle compute spend, while lifecycle rules automate transitioning aging media to cheaper archival storage classes without administrative overhead.
Adım Adım Çözüm
Anahtar Kavram
Cost Optimization through Serverless Compute Scaling and Automated Storage Tiering