Deploy your side-projects at scale for basically nothing – Google Cloud Run

Post by jon-wood » Sun, Jan 12, 2020, 9:32 PM UTC

abootstrapper wrote: post #152

matsz wrote: post #124

Earlier quoted context omitted.

Cloud hosting is great for businesses, that's why I believe that every web developer should experiment with those services. It's not great for personal use for the reasons you've stated - the risk of your service going down due to it being viral is much easier to bear than the risk of having to pay outrageous amounts of money for those services in that event. If your hobby project goes down for a while nobody will re…

Years ago I ran a side project that went viral. It grew to 60k visitors a day and my monthly cloud expenses were around $1,500. I cannot fathom a scenario where you get a surprise $100k bill from a viral hit. Anytime my project went down due to scaling, it was painful. You don’t get many chances at going viral.

Post by starptech » Sun, Jan 12, 2020, 9:36 PM UTC

unexaminedlife wrote: post #184

franciscop wrote: post #105

I have used it for work-related reasons and indeed the service is quite nice. But I don't use Google Cloud Run for personal projects for two reasons: - No way of limiting the expenses AFAIK. I don't want the possibility of having a huge bill on my name that I cannot pay. This unfortunately applies to other clouds. - The risk of being locked out. For many, many reasons (including the above), you can get locked out of…

I just did some math on their calculator: https://cloud.google.com/products/calculator/ I think some folks may be overestimating their ability to put a dent in Google's infrastructure. 1 CPU 2GB memory 80 concurrent requests per container instance 1000ms execution time per request 5kb outbound network bandwidth per request 100 million requests per month $120.19 per month What if we bump it up to 100kb per request? In…

Post by chewz » Sun, Jan 12, 2020, 9:47 PM UTC

unexaminedlife wrote: post #184

franciscop wrote: post #105

I have used it for work-related reasons and indeed the service is quite nice. But I don't use Google Cloud Run for personal projects for two reasons: - No way of limiting the expenses AFAIK. I don't want the possibility of having a huge bill on my name that I cannot pay. This unfortunately applies to other clouds. - The risk of being locked out. For many, many reasons (including the above), you can get locked out of…

I just did some math on their calculator: https://cloud.google.com/products/calculator/ I think some folks may be overestimating their ability to put a dent in Google's infrastructure. 1 CPU 2GB memory 80 concurrent requests per container instance 1000ms execution time per request 5kb outbound network bandwidth per request 100 million requests per month $120.19 per month What if we bump it up to 100kb per request? In…

Post by skj » Sun, Jan 12, 2020, 9:57 PM UTC

alasdair_ wrote: post #146

spyspy wrote: post #72

Earlier quoted context omitted.

You can deploy with a —max-instances flag to prevent infinite scaling. This has been a feature since the Cloud Run beta and has been in GAE forever.

One issue in GAE is that it can take 24 hours to update the billing cap. So if you happen to get a ton of fantastic press coverage one day, your site will go down and there is literally nothing you can do to fix it.

Post by Havoc » Sun, Jan 12, 2020, 10:09 PM UTC

alex-olivier wrote: post #41

Havoc wrote: post #32

Earlier quoted context omitted.

I thought GCP is alerts not capping?

The 'official' method is programmatically DIY! https://cloud.google.com/billing/docs/how-to/notify#cap_disa...