We were unable to load Disqus. If you are a moderator please see our troubleshooting guide.

Muhammad Junaid • 4 years ago

How is this different than container hosted on Azure app service?

Marko Anastasov • 4 years ago

For example there's no resource group to (over)allocate.

MikeDK • 4 years ago

Looks nice

Boogie Man • 4 years ago

Love the fact that Google cloud keeps improving & enhancing their services

robwaldron • 4 years ago

This blog seems misinformed. AWS Lambda and Azure Functions provide more than just run small functions. You can host a full ASP.NET Core service or NodeJS Express app in Lambda for instance. Cloud Run sounds nice, but isn't offering anything groundbreaking. Maybe Cloud Run is more akin to AWS Fargate?

Marko Anastasov • 4 years ago

No, with Fargate you start by provisioning a cluster (see https://twitter.com/kelseyh... which is not a serverless experience.

With Lambda you're programming _for Lambda_ specifically, and have to deal with CloudFormation, API Gateway... again UX that can be improved.

Jason • 4 years ago

Worth pointing out that AWS Lambda limits concurrent requests per instance to 1 (as does Google Cloud Functions). So while you can run an entire webapp in a function, it may not be the most optimal use of resources, and you typically hit a lot more cold starts which, if your app is large, can be slow. Cloud Run allows up to 80 concurrent requests on an instance (you can also force it to be 1 if you like). I believe Azure does allow concurrency to an instance.

Martin Dingus • 4 years ago

> The container listens for HTTP requests on port 8080.

This is incorrect. Cloud Run uses 8080 by default, but explicitly states you should not hard-code 8080, and should use the $PORT environment variable provided to the container instead.

Marko Anastasov • 4 years ago

Thanks for pointing that out. I don't see how it's incorrect as the port is "always set to 8080" but I've updated the article to recommend $PORT.