Live data from Hacker News

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

alexolivier.me

121–130 of 397 posts

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

#121

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…

Why not just make another Google Account just for this project?

It’s what I do since year, basically for every customer I work, I create a new account and even share the credentials with the customer (if he wants it).

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

#123

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.

people seem to forget the usage accrued via the devs themselves..

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

#124

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…

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 remember that and having to pay $100k will make you remember that for an eternity.

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

#125
post #65

Of course, the downside to doing anything with a Google product is that it could be deprecated next year...

Disclaimer: I work on Cloud Run as an SRE. Google Cloud has an official deprecation policy. If a product is labeled GA, Google Cloud guarantees that the service will continue running for at least 12 months since the announcement of deprecation.

Exactly. According to what you said, any service with that policy could literally shut down next year if there is a deprecation announcement this year.

Which is better than some small no name startup service provider who might just go out of business tomorrow, but among all the big cloud providers Google is definitely the hardest to trust with longevity.

A more realistic concern is that Google might substantially change the free tier making this more expensive, or might shut down some auxiliary product that would be painful to switch from without migrating clouds completely, or that a payment might bounce for some reason and now I’m locked out of all of my google services without recourse.

Sure the odds of all of the above are relatively low, but from what I’ve seen they are a lot higher on Google than they are on Azure or AWS.

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

#127

this has already been said, but due to the fact that this is google you have no idea when it's going to get killed and most things from google get killed. so i would suggest AWS. API Gateway + Lambda. It's basically free for side-projects and the setup + operating it is trivial. It also scales (and you're going to have to shell out real money) if you were to receive a lot of traffic.

Just the other day I wanted to buy a book, but Amazon no longer has it in stock...

Yes, that makes about as much sense as people who can't get over their favourite RSS reader, 13 years on.

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

#128

Of course, the downside to doing anything with a Google product is that it could be deprecated next year...

Can we standardize this standard comment? Say a URL that points to the problems we always see complaints about for using a Google service? Then someone posts that link at every Google HN post and we can all get on with our lives? They're boilerplate and don't add to the discussion.

Yes, as much as I agree with the sentiment of the GP, these comments really are just a bore now.

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

#129
post #93
post #17

The thing I really want out of these services is the ability to set a payment cap. It’s probably never going to be an issue, but I have anxiety, and I can’t sleep easily knowing that if I fuck up, if someone sinister abuses my application or whatever I may be stuck with a giant bill.

It's pretty complicated to do that on every services, imagine for any service they would have to call an API to get the $$ remaining , compute before scaling / creation if you have enough ect ...

If you wanted to be that precise, sure. But something like an hourly ‘calculate what I owe’ and compare it to a cap is not a big stretch of the imagination, and would suffice for many use cases.

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

#130

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…

Why not just make another Google Account just for this project? It’s what I do since year, basically for every customer I work, I create a new account and even share the credentials with the customer (if he wants it).

I’ve heard about Google correlating these accounts (through billing methods, contact methods, access patterns) and banning them together when one infringes on something. I’m not sure it’s the protection you think it is.
Post reply on HN