Live data from Hacker News

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

alexolivier.me

351–360 of 397 posts

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

#351
post #285

Do the kind of people who have tech jobs and have side projects really need it to cost nothing to run side projects? I don't understand this obsession with running projects for "nothing" and contorting software architecture to do so. $5/mo for a digital ocean droplet or $50/month for a a beefier VPS (or even dedicated hardware if you know where to look[0]) is not much compared to the normal monthly expenditure of peo…

While I tend to agree, I'm the type to have ~3 projects going at a time. I'm pretty young, but I can see myself spinning up a few projects a year. Each project needs a sql database, hosted by google for a few bucks a year, a server per service, a company email per project per person on the project, etc. I can easily see this being $50/month/project. So let's call it $150/month, $1800/year. If you're not making any mo…

You can do all of that with a $5/month vps assuming you don't get a ton of traffic.

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

#352
post #150

This article fails to mention the issue of needing a database. It doesn't matter how seamlessly your application can scale if your data backend won't scale with it. They mention Cloud SQL, which is of course instance based and would run into scaling issues if your app got suddenly hammered. Not to mention, the cost isn't $0 if your app gets 0 traffic, you are going to have to pay to keep that running around the clock…

A colleague keeps reminding me that in the end, if you don't need ACID, you can just use S3 as a key-value database and never pay more than pennies a month (and you get infinite scaling). Just depends if you need a db just for a few minor use cases or the app fundamentally depends on it

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

#353
post #308
post #51

Interesting. I've been looking looking at options too & opted for essentially the opposite: Get a big(ish) VPS and stack everything on top of each other with docker behind a nginx reverse proxy. So far so good. Managed to host gitlab, prometheus, grafana and ghost working this weekend, which I'm pretty chuffed about. Not as clean as OP's, but the intention was learning, so sacrifices on convenience are acceptable.

This is the advice I give early stage startups... don’t waste cycles learning the AWS stack, and getting locked in. Just pay for a cheap VPS, and scale it vertically as you grow. By the time you outgrow vertical scaling you should have the revenue or funding to figure out your at scale architecture. You’d be surprised how much you can handle with a single beefy VPS or dedicated.

A slight twist on this is a cheap, beefy colo box with nothing installed except something like k3s. This way you end up with all the YAML bureaucracy paid down in case that dreamy future with millions of users finally manifests

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

#354
YES with serverless you can really deploy your side projects at scale paying basically nothing if they don't get visited.

The Serverless Framework on AWS Lambda though are more mature to do that. One of the biggest gotchas is using just one aws lambda function with the entire web server instead of doing one aws lambda for each endpoint.

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

#355

Earlier quoted context omitted.

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".

What law do you think is preventing them from doing that already? Especially where US residents with no general privacy law are concerned?

The only thing that's preventing Google from telling their side of the story is their own refusal to engage human-to-human with individual customers.

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

#356
post #138

As a noob I have a question as to what advantages I have using docker compared to just a service like Heroku where I just push the application to them... and I don't bother with docker? To me with my limited understanding this seems like just another step. Now granted when it comes to work, I'm using docker with specifics that I know why I would want / can specify with docker ... but for personal projects this ever c…

Heroku build packs only work on Heroku. Containers work everywhere and they support any linux application.

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

#357
post #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 monthl…

Yes, Azure lets you set a per-Subscription spending limit.

It boggles the mind that AWS and GCP don't offer a payment cap - for that reason alone, I wouldn't go near them for side projects.

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

#358

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 had the same thoughts: even if I like Google Cloud a lot (I use it extensively at work), I don’t feel it’s safe for me to use it at home, since I don’t want to risk having my entire google account locked due to “suspicious activity”, whatever that might mean. In fact, I recently shut down a personal App Engine service I had been using for myself for a few years just because of this paranoia. The service was not doi…

The “oh noes!” Lock-in arguments are comical. Everything is lock-in. And it’s unlikely google makes some radical consumer change to screw people would hurt its efforts to be the #1 or #2 player. If we just focus on building on the things these cloud providers have built we can stop being leery about things and focus on the product and quit wasting cycles on things that don’t matter like the lock-in fear.

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

#359
post #355

Earlier quoted context omitted.

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".

What law do you think is preventing them from doing that already? Especially where US residents with no general privacy law are concerned? The only thing that's preventing Google from telling their side of the story is their own refusal to engage human-to-human with individual customers.

Both the law and Googles privacy policy stops them telling the world if you sent bomb threats to the president. That's still your private mail. They can't go looking it it, let alone telling the world about it.

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

#360

Earlier quoted context omitted.

I had the same thoughts: even if I like Google Cloud a lot (I use it extensively at work), I don’t feel it’s safe for me to use it at home, since I don’t want to risk having my entire google account locked due to “suspicious activity”, whatever that might mean. In fact, I recently shut down a personal App Engine service I had been using for myself for a few years just because of this paranoia. The service was not doi…

The “oh noes!” Lock-in arguments are comical. Everything is lock-in. And it’s unlikely google makes some radical consumer change to screw people would hurt its efforts to be the #1 or #2 player. If we just focus on building on the things these cloud providers have built we can stop being leery about things and focus on the product and quit wasting cycles on things that don’t matter like the lock-in fear.

You may have misinterpreted the comment chain. It sounds like you're talking about vendor lock-in. They're talking about being locked out of their Google account due to a Google bot incorrectly categorizing their work as spam or abuse. The implications for them being locked out is that they can't use anything related to their Google account. That could include their personal phone, personal email account and personal cloud services.
Post reply on HN