An organization is designing a serverless HTTP microservice to process uploaded financial documents. The workload requires running a specialized C++ processing tool packaged inside a custom container image, serving up to 50 concurrent HTTP requests per instance to optimize cost, and supporting request execution timeouts up to 30 minutes. Which Google Cloud serverless compute option should you recommend?
- Cloud Run, because it natively supports custom container images, multi-request concurrency per instance, and HTTP request timeouts up to 60 minutes.Cevap
- BCloud Functions (1st generation), because it provides the lowest cold-start latency for multi-threaded C++ binary containers.
- CCompute Engine Spot VMs in a Managed Instance Group, because serverless offerings on Google Cloud do not allow custom binary dependencies.
- DCloud Functions (2nd generation) with strict single-concurrency enforcement, because Cloud Functions is required whenever execution time exceeds 15 minutes.
Cevap
Cloud Run, because it natively supports custom container images, multi-request concurrency per instance, and HTTP request timeouts up to 60 minutes.
Cloud Run is the ideal choice for stateless containerized workloads that require custom Linux binaries, multi-request concurrency per instance to optimize operational costs, and HTTP timeouts up to 60 minutes.
Adım Adım Çözüm
Anahtar Kavram
Planning Serverless Compute Options (Cloud Run vs. Cloud Functions)
Tahmini Süre:1m 30s