Professional Cloud ArchitectDesign and plan a cloud solution architectureMedium
A media company needs to process large volumes of video files (terabytes daily) for transcoding, watermarking, and content analysis. These tasks are compute-intensive, can tolerate some processing delays, and are not user-facing. The company wants to minimize operational overhead and cost while ensuring the jobs are completed reliably. Which Google Cloud compute service is best suited for this workload?
- ACloud Batch
- BCloud Run
- CGoogle Kubernetes Engine (GKE)
- DCompute Engine with custom instances
Show answer & explanationAnswer & explanation
Correct answer: A. Cloud Batch
Cloud Batch is a fully managed service for running batch jobs, which aligns perfectly with the described workload: large volumes of compute-intensive, non-user-facing tasks that can tolerate delays. It handles infrastructure provisioning and scaling, minimizing operational overhead and optimizing cost.
Why the other options are wrong
- B. Cloud Run is ideal for stateless, event-driven web services or APIs, not large-scale, long-running batch processing tasks.
- C. GKE is excellent for containerized applications and microservices but introduces Kubernetes operational complexity which is overkill for simple batch jobs that don't require continuous deployment or service discovery.
- D. Compute Engine provides IaaS, requiring significant operational overhead for managing VMs, scaling, and job orchestration for batch processing.
Cloud Batch
A fully managed service for running batch jobs on Google Cloud, handling infrastructure provisioning, job scheduling, and scaling for high-performance computing workloads.
- Serverless batch processing
- Automates resource management
- Ideal for HPC, data processing, transcoding
- Cost-effective for intermittent, large-scale tasks
Memory trick: Batch processes: Set it, Forget it, Get the job done.