A financial technology enterprise is planning the serverless compute architecture for a financial statement rendering microservice on Google Cloud. The microservice must execute a proprietary, custom-compiled Linux binary packaged inside a container, and it must process up to 80 concurrent HTTP requests per instance to optimize compute costs and minimize cold starts. Which serverless compute option should the cloud engineering team select to meet these requirements?
- Cloud Run, because it supports running custom container images with arbitrary compiled binaries and allows configuring request concurrency per instance.Cevap
- BCloud Functions, because it automatically routes up to 80 concurrent HTTP requests into a single function execution context without containers.
- CCloud Functions, because custom compiled Linux binaries can only be executed using standard Cloud Functions language buildpacks.
- DApp Engine Standard Environment, because it is the only serverless service in Google Cloud capable of executing custom system binaries with concurrency.
Cevap
Cloud Run, because it supports running custom container images with arbitrary compiled binaries and allows configuring request concurrency per instance.
Cloud Run allows developers to deploy any container image, making it the ideal choice for workloads requiring custom-compiled Linux binaries. Furthermore, Cloud Run natively supports multi-concurrency, enabling a single container instance to serve multiple concurrent HTTP requests up to user-defined limits, satisfying both operational requirements efficiently.
Adım Adım Çözüm
Anahtar Kavram
Choosing Cloud Run for serverless container workloads requiring custom binaries and multi-request concurrency.