We've been using Firebase and one of the issues we had is that methods become "cold": if it's not used for a few minutes, the latency of the next call is unpredictable and could be in tens of seconds. The way Cloud Run is described ('Only pay when your code is running') suggests that it may suffer from it too. Does anyone know if it actually has the problem?
Deploy your side-projects at scale for basically nothing – Google Cloud Run
391–397 of 397 posts
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#392Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#393Earlier quoted context omitted.
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.
Had a VPS for side project at Vultr. First step first, could not send sign up emails from it.
Sounds like the problem was with the networking or application code. VPS can do anything when it's configured properly.
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#394Earlier quoted context omitted.
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.
Your deductible counts towards the out of pocket max
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#395Earlier quoted context omitted.
> No way of limiting the expenses This pattern seems common among business people: things working in the common case vs things working in corner cases, it’s how you end up with consumer windows running critical machines. I’m always shocked and moderately disturbed when I see it but I guess we all need to accept the reality that most people are very pragmatic. It makes sense, most people’s intuition comes from “the re…
Loss aversion[1] describes the phenomenon pretty well: > Humans may be hardwired to be loss averse due to asymmetric evolutionary pressure on losses and gains: for an organism operating close to the edge of survival, the loss of a day's food could cause death, whereas the gain of an extra day's food would not cause an extra day of life (unless the food could be easily and effectively stored). For lots of companies an…
That's not quite what I'm describing, it's more like how people will ignore git error messages and randomly fiddling with things thinking "that's just how it is and I can't understand it" rather than figuring out what's actually broken.
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#396This 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
Agree. Except I would keep in mind that AWS data egress is very expensive, so if there is any heavy media involved, you would also want to put a CDN in front of s3 with proper caching or you could find yourself with a hell of a bill from AWS.
So if you are serving up just a few megabytes and hit a few million page views you may find an AWS bill for a few thousand dollars.
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#397Earlier quoted context omitted.
Do you have examples of discontinued Google Cloud Platform products?
You don't need to ask me: Google provides their own handy list of examples (some like messaging API show up under other names like XMPP; others don't appear on this list because they were marketed differently, e.g. Google Print): https://cloud.google.com/appengine/docs/deprecations/
Those are just features of a single product (appengine) which has been around for more than a decade and through several generations. Every product under every cloud vendor has API and feature changes over the lifetime.
GCP has never had a major product line shutdown. The only thing that comes close is Google Maps API pricing changes, but technically the service is still there and has even more functionality.