Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

alexolivier.me

Post reply on HN
Print view View original

321–330 of 397 posts

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

#321

Post by onion2k »

Aeolun wrote: post #305
unexaminedlife wrote: post #184

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…

Just loading the Javascript for a basic React app is way over 100kb though.

It's 6kb for React and 25kb for React-DOM if you do a production build. Still a lot in terms of JS, but not quite as much as you're saying.

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

#322

Post by gvjddbnvdrbv »

LeifCarrotson wrote: post #197
joshvm wrote: post #194

Earlier quoted context omitted.

You can set up alerts if you exceed a budget, and you can program a response to turn off billing on a project. Google has a guide for doing exactly what you want. It's not a particularly clean fix, but it is fairly easy (copy paste) and can be done. It also allows for fine grain control eg you could kill an expensive backend process but keep the fronted running. You can also rate limit some APIs. https://cloud.google…

Is this not typical for...literally every use case? No one has an unlimited budget.

Google themselves recommend using the limits like max instances to mitigate the risk of out of control costs.

I also don't understand why this is being framed as a uniquely Google problem. Other cloud providers with serverless services have similar hazards and similar methods to manage the risk.

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

#323

Post by manigandham »

chrischen wrote: post #277
Polylactic_acid wrote: post #268

Earlier quoted context omitted.

I used to use google docs until they randomly locked one of the docs I was working on for a week due to one of their "suspicious activity" scripts. Really hammered in the message that if you don't host it then you don't own it.

I think the issue is you aren’t paying for it, so you don’t own it. Paid hosted services cannot pull this crap.

Quite a lot of paid services have done exactly this. They use vague all-encompassing terms of service designed to give them complete control. Pretty much anything can be used as a violation of those terms, allowing them to keep your money while also blocking all access and even deleting your data. Very few customers have the legal and financial resources to unblock this if it does happen.

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

#324

Post by zebnyc »

cutler wrote: post #271

For personal projects and client work I prefer a VPS with fixed pricing. Many have quoted Digital Ocean on this thread but you get much more for your money with a VPS from Hetzner.com. $11.75/month = 8Gb RAM, 2 CPUs, 80Gb SSD and 20Tb of traffic. That's 4 times the RAM, 2 times the CPU and 10 times the traffic compared with a $10 Digital Ocean VPS.

Does Hetzner.com have servers based in the US?

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

#326

Post by manigandham »

gvjddbnvdrbv wrote: post #316
franga2000 wrote: post #303

Earlier quoted context omitted.

Paid G suite can and does pull this crap. There was a comment on HN a year-ish ago, when someone's entire ~100 person company (almost?) went out of business because Google flagged the personal Gmail of the domain admin, this "spread" to their company email, Google closed it and losing the admin account made the entire domain get deleted. Not "blocked" or "pending review" - deleted! IIRC even pulling personal favors a…

Do you have a link to this story?

Here's a few:

https://news.ycombinator.com/item?id=17115643

https://news.ycombinator.com/item?id=19124324

https://news.ycombinator.com/item?id=19432702

https://news.ycombinator.com/item?id=21247759

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

#327

Post by zaphirplane »

erdemozg wrote: post #320
nine_k wrote: post #296

Earlier quoted context omitted.

If I were to run any public-facing protect on Google Cloud, I definitely would use a separate account, created just for that. You never knows what might happen to that account. I thought everybody does this. I wonder how hard would it be to run a script that checks your balance e.g. every 15 minutes, and shuts down public access to your services when a certain threshold is triggered. I wonder if a ready-made service…

Google somehow is able to link your newly created account to your personal/regular account. So if you some shady stuff with the new account, your other account is at risk of being locked out, too.

Has anyone gone down an account per side project and not gotten into a problem? And is there a warning before the banning sledge hammer falls

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

#328

Post by Mirioron »

tluyben2 wrote: post #315
Mirioron wrote: post #217

Earlier quoted context omitted.

It's possible to write bug-free code, but would you bet your financial future on your ability to write bug-free code?

Bug free is a not realistic but if you are a programmer and definitely if you are a tech founder you definitely should be willing to bet your financial future on writing reasonably low bug code. If you are a programmer, I kind of find the comment puzzling; maybe I am reading you wrong, but you seem to be saying that you are writing code for some company while being happy to commit it and not care if the company loses…

When you work for somebody else (or with somebody else) then you try to do as good of a job as possible, but the ultimate responsibility still lies elsewhere - might be your boss or could even be the group. There will be other people who interact with your code and might spot errors. There will be people who are trained, in some capacity, to figure out ways to mitigate against accidentally generating very large bills. It is exceedingly unlikely that these points hold true for a solo developer working on a main project, let alone a side project.

Even if you are hyper competent and can probably get all of this correctly, you can't rest easy. You simply don't know whether you did everything correctly or not. Just one dumb mistake can saddle you with an enormous bill.

This is just like gun safety: don't point your gun at anything you're not intending to shoot. Mistakes happen and the consequences of it can be catastrophic.

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

#329

Post by manigandham »

tluyben2 wrote: post #318
StillBored wrote: post #104

Earlier quoted context omitted.

These stories are everywhere. A couple months ago, it hit an associate of mine pretty hard, he moved a small python monitoring and statistics application off a laptop in the office to AWS. A couple weeks later he came back and discovered that it had burned up a few thousand $'s in storage and transfer fees for what normally was a couple hundred MBs of data a day being passed around and a some database updates. Since…

Virtual cards with limits are an answer to this. Works very well.

Not really. You're still responsible for the bill even if your payment method is capped. They don't just forget about it.

If you never pay then expect some aggressive account shutdown, bans across all connected user accounts, and calls from debt collections.

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

#330

Post by Mirioron »

D2187645 wrote: post #245
Mirioron wrote: post #217

Earlier quoted context omitted.

It's possible to write bug-free code, but would you bet your financial future on your ability to write bug-free code?

Starting to think the reason we arnt working for google/aws is we make mistakes. Whereas engineers at those companies just dont make mistakes, therefor they assume that billing caps are not necessary. Such is our lot in life.

I think the bigger difference (other than a potential skill difference) is rather that they're more willing to take these risks. The ones that are good at it and succeed will rise to the top!
Post reply on HN