Earlier quoted context omitted.
Cost is not only based on the number of instances. From a quick search: https://www.jhanley.com/google-cloud-run-pricing/ Understanding the cost of these services is not easy at all, especially for extreme cases/situations. And a calculator/estimator won't fix the problem. That is why I love the fixed $X/month where there's no room for surprises.
I hope GCP/AWS add a max spend ability. Until then it's complexity of pricing model vs time spent on OS and database management. To each their own.
Deploy your side-projects at scale for basically nothing – Google Cloud Run
191–200 of 397 posts
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#192I 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…
Welcome to US healthcare. Happens daily! :)
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#193Earlier quoted context omitted.
This sounds like a short term 'thinking'. If there are a few stories on the internet (and there are some in this very thread) about developers getting burned by this 'feature', it would turn off a lot of potential users in the future. It would make sense to be transparent and give tools to strictly control usage/billing - both in terms of trust and money.
It is. I'm using free there to build and host my projects. If/when I exceed the free tier I'm not making a billing account unless I can set a max bill. I'll sooner rewrite everything to run on bare metal that has a fixed monthly cost.
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#194I 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…
You can also rate limit some APIs.
https://cloud.google.com/billing/docs/how-to/notify#cap_disa...
> You might cap costs because you have a hard limit on how much money you can spend on Google Cloud. This is typical for students, researchers, or developers working in sandbox environments. In these cases you want to stop the spending and might be willing to shutdown all your Google Cloud services and usage when your budget limit is reached.
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#195Earlier quoted context omitted.
https://scaleway.com prices their base compute very cheap [0]. They have got DCs in AMS and CDG, but unfortunately, I've not got to use them since their DCs are a bit far from customers. [0] €2.99 for 2vCPU, 2GB RAM, 200Mbits/s bandwidth.
75GB object storage free??? Am I reading this correctly or am I stupid?
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#196I 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…
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#197I 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…
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…
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#198I wont use this for the simple reason that I bought into the Google Appengine stack in the past and it really bit me for several reasons: They force-upgraded the java version. The problem was their their own libraries didn’t work with the new version and we had to rewrite a ton of code. It ended up being insanely expensive at scale. We were totally locked-in to their system and the way it did things. This would be fi…
App Engine was the very first PaaS, came out before Docker, and did things very uniquely in order to try to only allow scalable apps. App Engine standard has to explicitly create special environments for each of their runtimes, and that's slow and expensive. Services like Datastore and Memcache were tightly coupled.
Cloud Run fixes all that. It's just a Docker container that listens on the PORT env variable. Use whatever runtime you want. Run the same container locally, or on another cloud provider. The other services like Firestore or Memorystore (Redis) are truly optional and external.
Cloud Run is what lets you avoid single-vendor lock in, but still get from 0 scaling.
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#199I 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 cannot have a $100k bill to pay, it'd destroy everything I have. Welcome to US healthcare. Happens daily! :)
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#200Earlier 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…
I ordered a phone from Google that's been lost in delivery. I have Gmail/documents/photos/music... Should I do a charge-back? Sue them in small claims court? I should never have done business with them.
Google's algorithm can flag a chargeback as suspicious, leading you to be locked out.