3 ms·

Am I reading pricing right, that it is $0.40/million requests beyond free quota versus $3.50/million (first 333 million) on AWS API Gateway? One thing that alw

Am I reading pricing right, that it is $0.40/million requests beyond free quota versus $3.50/million (first 333 million) on AWS API Gateway? One thing that always killed AWS Lambda/APIG for our use cases was the API Gateway request pricing. This seems much better. I love that you can just run Docker containers. My one wish is the option to run on multiple regions at once with Anycast or similar. I haven't tested yet to see what extra latency or cold start times this may have. That is the other thing that bothers me about Lambda.

hn_throwaway_99 8y ago
FWIW Cloud Run seems much more analogous to AWS Fargate than Lambdas.
sudhirj 8y ago
AWS has enabled calling Lambdas from the Application Load Balancer, you no longer need to use API Gateway.
asciimike 8y ago
> that it is $0.40/million requests beyond free quota versus $3.50/million (first 333 million) on AWS API Gateway Comparing Run to API Gateway is a bit apples to oranges, as one is a managed compute product and the other is an API management product. Run (and GCF, and GAE) automatically provision an HTTP endpoint for you so you aren't required to use an API management product like Cloud Endpoints. However, they don't provide API key validation, rate limiting/quota, schema validation, etc. which is what you're paying for (even if you're not using them) with API Gateway. A more apples to apples comparison would be something like: - Cloud Run ($0.40/M) + Cloud Endpoints ($3.00/M) = $3.40/M - Lambda ($0.20/M) + API Gateway ($3.50/M) = $3.70/M > My one wish is the option to run on multiple regions at once with Anycast or similar. We're working on GCLB (https://cloud.google.com/load-balancing/ https://cloud.google.com/load-balancing/) integration, which will let you create multi-regional or global service.
- johne20 8y ago
  Thank you for your response, that definitely helps me understand the differences. In our particular higher volume use cases, we handle the rate limiting/key validation ourselves so I like that Run automatically provisions a HTTP endpoint.

hn_throwaway_99 8y ago

FWIW Cloud Run seems much more analogous to AWS Fargate than Lambdas.

sudhirj 8y ago

AWS has enabled calling Lambdas from the Application Load Balancer, you no longer need to use API Gateway.

asciimike 8y ago

> that it is $0.40/million requests beyond free quota versus $3.50/million (first 333 million) on AWS API Gateway Comparing Run to API Gateway is a bit apples to oranges, as one is a managed compute product and the other is an API management product. Run (and GCF, and GAE) automatically provision an HTTP endpoint for you so you aren't required to use an API management product like Cloud Endpoints. However, they don't provide API key validation, rate limiting/quota, schema validation, etc. which is what you're paying for (even if you're not using them) with API Gateway. A more apples to apples comparison would be something like: - Cloud Run ($0.40/M) + Cloud Endpoints ($3.00/M) = $3.40/M - Lambda ($0.20/M) + API Gateway ($3.50/M) = $3.70/M > My one wish is the option to run on multiple regions at once with Anycast or similar. We're working on GCLB (https://cloud.google.com/load-balancing/ https://cloud.google.com/load-balancing/) integration, which will let you create multi-regional or global service.

johne20 8y ago
Thank you for your response, that definitely helps me understand the differences. In our particular higher volume use cases, we handle the rate limiting/key validation ourselves so I like that Run automatically provisions a HTTP endpoint.