A cloud engineer at a digital media firm is designing the serverless architecture for a web utility that processes image rendering requests. The application relies on a custom compiled C++ binary and specific Linux system libraries that are not included in standard language runtime environments. Additionally, the workload requires handling multiple concurrent HTTP requests per instance to optimize resource usage and reduce cold starts. Which Google Cloud serverless compute option should the engineer select?
- Cloud Run, because it allows deploying custom container images containing any system binary and supports setting concurrency to process multiple requests per container instance simultaneously.Cevap
- BCloud Functions, because it automatically packages custom C++ system libraries directly from raw source code and distributes incoming HTTP requests across threads.
- CCloud Functions (2nd gen), because 2nd gen functions eliminate the need for containerization while allowing custom binary installations via cloudbuild.yaml deployment files.
- DCompute Engine Unmanaged Instance Groups, because serverless platforms on Google Cloud cannot run custom compiled binaries or system-level dependencies.
Cevap
The cloud engineer should select Cloud Run because it supports custom container images with arbitrary compiled binaries and allows multi-concurrency per container instance.
Cloud Run is designed to execute stateless OCI-compliant container images. This allows developers to package custom C++ binaries, system libraries, and system configurations. Furthermore, Cloud Run instances can process multiple concurrent requests simultaneously on a single instance, meeting both operational requirements.
Adım Adım Çözüm
Anahtar Kavram
Selecting Cloud Run versus Cloud Functions based on containerization requirements, custom binaries, and request concurrency