[nojvek]

Yesssss. Right now I have a cron that hits my app every minute to keep it warm. However even with that I see cold starts every now and then. This removed that problem.

It’s so surprising that AWS and Azure don’t have an equivalent to GCP cloud run.

Being able to run a container on demand with a custom image with whatever language and dependencies you want is amazing.

I’ve spun up browsers for snapshotting and seeing a page like a real browser. Cloud run scale from 0 is absolutely magical.

This is what serverless ought to be. Cloud run + firestore makes it possible to build pretty scalable apps with little effort and pretty cheap to run.

[jtsiskin]

Yeah this setup is the biggest advantage I see to the cloud vs self hosted - the possibility of far more efficient resource usage due to things like cloud run, lambda, etc.

I dream of a day when the underlying “cloud” is completely commoditized and interoperable, and your code will run wherever is cheapest, and the cost actually becomes less than self hosting.

[inishchith]

Agree with most points made. Though interested to know where's your cron running? - is it one of your self-hosted servers or are you using some service for it like freshping.io?

[nojvek]

Use google cloud scheduler for the cron. It’s the most expensive part of my stack at 15c/month.

[digianarchist]

AWS added container support to Lambda recently.

[nojvek]

It’s not the same as cloud run though. Cloud run just needs a thing listening on $PORT environment variable. That’s the only interface needed to the container. The rest is totally agnostic to knowing that it’s inside cloud run.

[digianarchist]

Ah I see. So there's no need to write an interface that accepts the event object? It's all HTTP on Google Cloud Run?

Do you have to gracefully shutdown the container or does Google just kill the container once it gets a response?