Live data from Hacker News

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

alexolivier.me

231–240 of 397 posts

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

#231
post #225
post #83

Earlier quoted context omitted.

Do you have examples of discontinued Google Cloud Platform products?

You don't need to ask me: Google provides their own handy list of examples (some like messaging API show up under other names like XMPP; others don't appear on this list because they were marketed differently, e.g. Google Print): https://cloud.google.com/appengine/docs/deprecations/

Many of those seem to have been around for well more than the 1 year deprecation minimum, and most of them appear to be some combination of Alpha/Beta products or language runtimes. Alpha/Beta products aren't really on-topic, and the language runtime stuff doesn't look all that different from how AWS does runtime deprecations.

https://docs.aws.amazon.com/lambda/latest/dg/runtime-support...

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

#232

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 agree about being too scared to do business with Google. FWIW, I have a project that monitors an AWS S3 hosted web site every minute and takes it down if the charges exceed a quota. It ends up costing me 44 cents a month to run it as a lambda function but I think of it as insurance. Pull requests are welcome from whoever understands Terraform better than me because I couldn't figure out how to automate everything about the deployment.

https://github.com/gueststar/s3quota

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

#233

Earlier quoted context omitted.

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…

Your setup is unrealistic. 100 million requests per month with 80 concurrent requests?. 1000 $ is cheap if you try to run wikipedia.com fully managed.

A lot of web stacks optimize for concurrency. Based on 2GB memory, which ends up being ~25MB per request (which for me is extremely high), I don't see it as being unrealistic. Especially for the use case I'm considering. Typically the only reason these boxes exist is to allow a web browser to gain access to data in a database, so most of the 1000ms per request wouldn't be spent in CPU, it will be spent waiting for the database to return a response.

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

#234
Can't you see this article is a paid advertisement for Google Cloud? Just like those 1 hour long videos on youtube - where they show how pilots fly an airplane of a specific company and how well is al organized or a 1 hour long video of a german car factory.

Just reading this line makes you suspicious: "I have built hundreds of side projects over the years "

really? Hundreds?

And then below:

"I am yet to have a side project go ‘viral’"

Out of hundreds of projects over the years, none of them went viral?

And if you look at his "blog" you will see it has 3 entries in total: https://alexolivier.me/

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

#235

AFAIK, PaaS solutions like heroku have a similar way of working, at least for side-projects. Here, you deploy a container and Google runs it somewhere and Heroku containerizes your application every time you push it. Similar to here, Heroku's free hobby containers also go to sleep in ~30min inactivity.

Fixed with: https://kaffeine.herokuapp.com

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

#237
post #8

Cloud run is what zeit now was before it moved to v2. https://zeit.co/

What does it run on today? Or, is it multi-cloud now?

yep, multi-cloud https://zeit.co/docs/v2/network/regions-and-providers/

You can specify where to deploy to in a config file. Pretty cool stuff.

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

#238

Earlier quoted context omitted.

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…

I'm not from the US, and the thought of "only" paying $1071/m for a side project which is most likely not generating revenue is mindblowing. If you give me $1071-$120 = $951/month forever for optimizing an app once I'll optimize it for you :)

I can't say it's "only" $1071/month. I definitely wouldn't go broke because of it though. Especially if it's only a side project I probably would look for ways to reduce cost for subsequent months.

I don't know how optimizing comes into the equation. The app you build and deploy to Google Run leverages their infrastructure. A fiber optic cross (with just one telecommunications company) connect would cost probably close to $1000/month alone, but Google is probably peered with every telecommunications company in the entire world, and they don't have just one fiber optic line connecting to each of them. So, it's not really a one-time optimization when you put your work on Google. It's like I would be paying Google $1071 to rent the infrastructure of their entire network to receive and distribute data in my name.

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

#239

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'd much rather overpay $20-50/month

I don't think the alternatives are nearly that expensive. Vultr, DigitalOcean and others have virtual private servers for only $5 per month. They're small instances but totally fine for side-projects. I run a cheap $5/month VPS and it was able to withstand my project making the HN front page without issues. I don't use Google cloud hosting for the same reasons as you, I don't want to have too many eggs in one basket.

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

#240

As an illustrative of pricing: If your deployment can run in 256MB of RAM w/ 1 vCPU, handles an average request in under 250ms, transfers 200kb or less per request on average, and you get 2 requests/minute on average to your site: The cost is around $2/month USD, which I feel is a more likely scenario for a side project vs the “pennies a month” the OP claims.

"2 requests/minute on average to your site" is a bad assumption for a relatively unpopular side project. More importantly, with those hypothetical numbers, you'd stay well within the free tier for compute.

2 requests/minute = 86400 requests a month. Plug in the other numbers from my earlier post and you’ll see the calculator say exactly as I said, around $2/month give or take depending on region.
Post reply on HN