Live data from Hacker News

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

alexolivier.me

331–340 of 397 posts

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

#331
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.

Are there any cloud products that have hard $$$ caps? Even non-big 3. Any at all?

Seems like this is a huge dealbreaker. You cannot be expected to perfectly audit your side project for security. Suppose someone finds a remote code execution and starts mining Monero on it. Or someone just points a botnet at it. You could be on the hook for an unlimited amount of money.

Might as well just install Kubernetes on a monthly-fee VPS and pretend you're using GCP.

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

#332

Earlier quoted context omitted.

A “cap” feature isn’t as easy to implement as you’d think. What happens when you hit the cap? Does it start shutting down instances? If yes, which ones and in what order? And don’t say “I don’t care” because you do care—you are allowing your provider to basically cause an outage in your service. If you do allow some kind of ordered shutdown of service, what is the UX going to look like? What is the API going to look…

Why not allow people to set a cap that disables everything set to that billing method once it's been reached? That seems to be the use case that people are saying is missing from cloud offerings.

Things like storage (disks or S3) continue to incur costs even if the instance is shutdown. Should they just delete your data too?

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

#333
post #311

Earlier quoted context omitted.

A “cap” feature isn’t as easy to implement as you’d think. What happens when you hit the cap? Does it start shutting down instances? If yes, which ones and in what order? And don’t say “I don’t care” because you do care—you are allowing your provider to basically cause an outage in your service. If you do allow some kind of ordered shutdown of service, what is the UX going to look like? What is the API going to look…

What is the API going to look like? Maybe just a simply array with the list of services to be shut down in the order provided? This should be enough for hobby and smaller projects, bigger projects will have plans/people in place anyway. It is not that they can't do it - we are talking about a company with insane technical ability and resources. It is just that they don't want to do it.

What would you like to do with your VM disks and/or object storage when you hit the cap? Delete them?

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

#334
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...

This is ridiculous. I'm guessing a huge revenue source is going after businesses for long-tail billing spikes.

Not only do I have to worry about bad code causing a huge bill, I also have to worry about the quality of code (or config) that emergency stops the billing.

I wonder if you can sign up with a pre-paid credit card and use a fake name.

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

#335

Earlier quoted context omitted.

Happens even with insurance.

The max out of pocket is about $8k under the ACA. That is a lot of money for a lot of people, but it isn't nearly $100k

There are a bunch of costs that could increase this number: having to deal with networks, having an emergency and having the max amount for a procedure exceeded, and, in some cases, your deductible.

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

#336
post #226

This is exactly the service that Azure needs and doesn't seem to have: while there is a consumption plan for functions, that's about it, and App Service is incredibly expensive for what you get.

As @GordonS mentions, Azure Container Instances is about as close as you’ll get with Azure, but it’s only close on ease-of-use: rather different from a deployment/scaling characteristics POV. I’m generally very underwhelmed by Azure offerings, but ACI is one of the few that actually lives up to what is advertised.

Yeah, I did look at that, and I think you're right on ease-of-use - it's a deploy and done deal, which is nice. I think it suffers from two things:

* the cost seems net-net similar to App Service, but more granular. So I can go this route and get slightly more flexible pricing, but at the cost of some arbitrary limits on assignable CPU/memory.

* it's easy to wander into Azure Container Service stuff accidentally, and that has "deprecated" plastered all over it. Shame the naming doesn't separate them more clearly.

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

#337

Earlier quoted context omitted.

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

Google's main problem here is they can't tell their side of the story.

If only they had some process where a customer could agree to have Google publicly explain why an account was banned, I think we'd see many more explanations along the lines of "This customer was using Google cloud to launch Ddos attacks" or "This customer sent bomb threats to the president".

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

#340
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 doesn't have good enough billing systems to be able to guarantee to be able to limit your spend. Lots of billing things are only done daily for example, meaning you could spend millions of dollars before the billing run at the end of the day.

Google prefers you be on the hook rather than them.

Post reply on HN