Live data from Hacker News

Cloud Run adds min instances feature for latency-sensitive apps

cloud.google.com

21–30 of 65 posts

Re: Cloud Run adds min instances feature for latency-sensitive apps

#21

Wondering where this magic lives in the stack. Is this possible in Knative? Just elaborate ctl-Z?

> Is this possible in Knative?

Yes: https://knative.dev/docs/serving/autoscaling/scale-bounds/#u...

I also wrote about it: https://livebook.manning.com/book/knative-in-action/chapter-...

Re: Cloud Run adds min instances feature for latency-sensitive apps

#22

This is probably not a response to the other story this week about a start-up that got a $70k bill from Google cloud erroneously: https://news.ycombinator.com/item?id=25372336

How would a min amount of cloud run processes be a response to a billing issue born from a series of unfortunate events?

Re: Cloud Run adds min instances feature for latency-sensitive apps

#23

This is probably not a response to the other story this week about a start-up that got a $70k bill from Google cloud erroneously: https://news.ycombinator.com/item?id=25372336

This feature doesn't cap your costs. It's to reduce/eliminate cold start times for your containers.

Re: Cloud Run adds min instances feature for latency-sensitive apps

#24
post #12
post #9

AppEngine has had scale-to-zero for 15 years, but instead of having a coherent product strategy, why not just launch a different competing product every year which is missing features that already exist? AppEngine vs Cloud Functions vs Cloud Run, the reasons these all exist at the same time is not because it makes any sense for customers, but because Google PMs get promoted for launching new things rather than suppor…

I disagree. App Engine is nothing like Cloud Functions/Run. The former is a better fit for your entire app stack (think Heroku) while the latter is for ad-hoc. As for Cloud Functions and Cloud Run, the way you deploy is completely different. Cloud Run is strictly meant for containers.

> App Engine is nothing like Cloud Functions/Run.

This isn't true. App Engine Flexible is in fact very similar to Cloud Run, and my understanding is that it runs on the same infrastructure. In fact, App Engine Flexible "Custom Runtime", which lets you load a docker container in App Engine, is very similar to Cloud Run.

FWIW, though, as a user of App Engine Flexible for Node, I'm very glad this Cloud Run option now exists.

Re: Cloud Run adds min instances feature for latency-sensitive apps

#26
post #14
post #9

AppEngine has had scale-to-zero for 15 years, but instead of having a coherent product strategy, why not just launch a different competing product every year which is missing features that already exist? AppEngine vs Cloud Functions vs Cloud Run, the reasons these all exist at the same time is not because it makes any sense for customers, but because Google PMs get promoted for launching new things rather than suppor…

Worse than that. Its AppEngine Standard vs AppEngine Flex vs Cloud Functions vs Cloud Run vs KNative (Cloud Run, but different). Oh and if you used AppEngine Standard, you can't move to Flex as Flex came with a whole new set of libraries. And Flex to CloudRun didn't exactly have a seamless migration. Along the way they changed multiple internals with deprecation causing code base changes. Such-as Memecache, ImageAPI,…

Everything above. Friends don't let friends use App Engine, and by extension, fringe GCloud services they could break or shitcan at literally any moment

The technology of a vendor is way less important than its culture. So far Gcloud seems to understand that. Maybe the App Engine team is outside that org

Re: Cloud Run adds min instances feature for latency-sensitive apps

#27
post #4

So if there's something always running .... isn't the same as having on always on server (with auto scaling of some sort)?

It seems they want to replace their managed AppEngine service through Cloud Run in the long run.

Cloud run is developed by the same team that built AppEngine. They share the same technical leadership and a lot of the technical stacks, for example, billing and security (gVisor).

I dont think it's that simple to replace one service with another. It requires a lot of very sensitive dealing with external customers. And one cannot (easily) use the typical "Google deprecation" on a Cloud service offering, either.

So it's complicated. But your impression is not too far from the inclination.

Re: Cloud Run adds min instances feature for latency-sensitive apps

#28
post #13
post #12

Earlier quoted context omitted.

I disagree. App Engine is nothing like Cloud Functions/Run. The former is a better fit for your entire app stack (think Heroku) while the latter is for ad-hoc. As for Cloud Functions and Cloud Run, the way you deploy is completely different. Cloud Run is strictly meant for containers.

I don't think the 3 products are serving as diverse a set of use cases as you think... > The former is a better fit for your entire app stack (think Heroku) while the latter is for ad-hoc. There's no product reason why App Engine couldn't start deploying custom containers. > As for Cloud Functions and Cloud Run, the way you deploy is completely different. Cloud Run is strictly meant for containers. AWS Lambda (arguab…

> There's no product reason why App Engine couldn't start deploying custom containers.

There better not be because it already does: https://cloud.google.com/appengine/docs/flexible/custom-runt...

Re: Cloud Run adds min instances feature for latency-sensitive apps

#30

This is a response to this AWS Lambda launch, over a year later: https://aws.amazon.com/blogs/compute/new-for-aws-lambda-pred...

Cloud Run is for containers, not functions, and it's the next evolution of App Engine.

The GCP equivalent to Lambda is Cloud Functions.

Post reply on HN