Quick comparison
| Criterion | Google Cloud Run | AWS Lambda | Comparability note |
|---|---|---|---|
| Maximum service/function time | Google Cloud Run60 minutesCloud Run servicesGoogle Cloud | AWS Lambda900 seconds (15 minutes)A function-level configuration ceiling; the configured timeout may be lower.Amazon Web Services | Cloud Run's value is an HTTP service request timeout; Lambda's is the whole function invocation. |
| Ordinary HTTP/synchronous payload | Google Cloud Run32 MiB request; 32 MiB non-streamed responseHTTP/1 servicesGoogle Cloud | AWS Lambda6 MB eachAWS uses MB in Lambda docs to mean 1,024 KB.Amazon Web Services | Cloud Run varies by HTTP version and streaming; Lambda has separate async and streamed response modes. |
Which is best for your requirement?
Its documented maximum service/function time scope fits your measured workload and the caveats shown in the comparison.
Its documented execution or account model better matches the exact requirement rather than a vendor-wide headline.
Test payload, duration, throughput, concurrency, failure behavior, billing scope, and recovery with representative traffic.
Validate the decision with your workload
Before choosing between Google Cloud Run and AWS Lambda, reproduce the comparison with the exact plans, models, regions, runtimes, and invocation paths you intend to operate. The reviewed rows cover maximum service/function time and ordinary http/synchronous payload; they do not turn different pricing, reliability, developer experience, or ecosystem tradeoffs into one universal score.
- Capture representative request sizes, token usage, duration, concurrency, storage, and failure behavior at realistic percentiles.
- Test the boundary and the recovery path on both candidates, including throttling, timeouts, partial failure, retries, and cost controls.
- Record which scoped observation drove the choice and recheck its official source before migration or a major traffic increase.