Live data from Hacker News

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

alexolivier.me

41–50 of 397 posts

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

#41
post #32

Earlier quoted context omitted.

Do-able today with GCP Billing

I thought GCP is alerts not capping?

The 'official' method is programmatically DIY!

https://cloud.google.com/billing/docs/how-to/notify#cap_disa...

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

#42
I often find myself what "at scale" means. It is used by so many different providers and it gets confusing.

When all you give the service is a container, how dos it know how to scale your project?

I presume it gives it more CPU and more RAM automagically but does that really provide "at scale"

I think of "at scale" to mean really a lot of traffic.

Spinning up new instances if your container is possible, but I think I would like an API where code can somehow interact with the scaling mechanism.

I guess "stateless" gives us some information.

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

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

Do-able today with GCP Billing

[deleted]

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

#44
post #24

Excuse my ignorance. if a container hasn't been hit in a long time, how long does it take to serve the first request back? Is it spun up or sort of hot paused?

It depends on the size of the container, but it can be a few seconds for a cold boot if small, then instantly for requests soon after that.

Unfortunately Cloud Run obfuscates when a cold boot is necessary.

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

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

This makes me anxious as well.

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

#46
If you already have an EC2 instance reserved on AWS for a year, you could just throw all those small projects there.

If they are truly stateless then the bottleneck will probably be the database, anyway.

For anyone starting a new app I recommend just building apps that are TRULY serverless. Then you can make them client-first, work offline, not tied to on one particular domain name, support end-to-end encryption, be embarassingly parallel and scalable, and take an activist position against continuing centralization.

A fuller exposition is here, so I don’t have fo write a whole mountain of text: https://qbix.com/blog/2020/01/02/the-case-for-building-clien...

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

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

Set budget alerts. And check what's going on if they start going off.

Or think again if you really need 'infinitely scalable bla blah' for personal project on a small budget.

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

#48
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 cheap insurance to create an LLC to protect yourself from extreme situations for this kind of thing. Worst case the LLC goes defunct, but you won't be personally liable. https://www.nolo.com/legal-encyclopedia/limited-liability-pr... EDIT: This comment is based on the assumption that the parent was trying to start a side business. I'm certainly not advocating fraud.

wut? are you suggesting that if there's a cost overrun you just shutdown the LLC? that sounds like a loop that couldn't possibly be true? when you sign TOS you agree to be responsible for service fees. if being an LLC indemnifies against these sorts of charges it would also indemnify you against other legitimate fees? take out a business credit card and cash advance and then close the LLC? free money!

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

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

haha

>Warning: This example removes billing from your project, shutting down all resources.

this is the digital equivalent of literally pulling the plug. i wonder how long it takes for GCP to register that you've pulled billing though? in some cases i'm sure even milliseconds could make a large difference.

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

#50

What’s the advantage of GCR over AWS Fargate/ECS? I’ve been running an app on ECS for a couple months now and have been pretty happy with the ease of set-up, load-balancing, auto-scaling etc, though there are still kinks I’m figuring out (SSHing into containers to perform database management, for example, or deploying updated tasks without downtime). Is the main selling point of GCR just its price? I haven’t found EC…

GCR runs containers like Fargate, but scales to zero like lambda, so you only pay for usage
Post reply on HN