CDN, edge compute & global acceleration · AWS vs Google Cloud
Lambda@Edge: Google Cloud equivalent
Google Cloud has no full serverless function runtime at the CDN edge like Lambda@Edge.
Use Service Extensions callouts to Cloud Run, or run logic in Cloud Run behind the load balancer.
Side-by-side comparison
| Aspect | Amazon Web Services | Google Cloud |
|---|---|---|
| Service | Lambda@Edge | No first-party equivalent |
| Lifecycle | Generally available | — |
| What it is | Node.js or Python Lambda functions authored in US East (N. Virginia) and run at AWS locations close to viewers, triggered on CloudFront viewer and origin requests and responses. | — |
| Pricing model | Per request plus duration in GB-seconds (higher rates than regional Lambda). | Not applicable. |
| Docs | Lambda@Edge docs | — |
| Pricing page | Lambda@Edge pricing | — |
Key differences
- Callouts send requests to a backend service you run, not to edge locations.
Pricing summary
Pricing models only. No prices are quoted because they change by region and over time.
- AWS
- Per request plus duration in GB-seconds (higher rates than regional Lambda). Lambda@Edge pricing →
- GCP
- Not applicable.
And on Azure?
No equivalent Azure has no first-party equivalent. AWS vs Azure comparison →
FAQ
Does Google Cloud have an equivalent to Lambda@Edge?
Google Cloud has no full serverless function runtime at the CDN edge like Lambda@Edge. Use Service Extensions callouts to Cloud Run, or run logic in Cloud Run behind the load balancer.
How does pricing compare between Lambda@Edge and Google Cloud?
AWS: Per request plus duration in GB-seconds (higher rates than regional Lambda). Google Cloud: Not applicable. Check the official pricing pages for current rates.
What is the Azure equivalent?
Azure has no first-party equivalent. Azure has no equivalent of Lambda@Edge.