Cloud Run adds min instances feature for latency-sensitive apps • Hacker News Board

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

#61

Post by jkaplowitz » Sat, Dec 12, 2020, 8:53 PM UTC

baskire wrote: post #47

jkaplowitz wrote: post #44

Earlier quoted context omitted.

> 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 Not sure why you think they can shitcan them at literally any moment. Although GCP's track record of deprecation is of course far worse than AWS's, they do make and adhere to promises in their terms of service that, in most cases, they will give at least 12 months…

That’s false. The policy only covers services being turned down. A-la Google reader style. Not api changes. Not forced sdk/software upgrades. Or pricing changes.

It does cover backwards incompatible API changes - read the second link I provided:

>Further, Google will notify Customer at least 12 months before significantly modifying a Customer-facing Google API in a backwards-incompatible manner.

What are you referring to with forced sdk/software changes? Maybe it's the same exception I mentioned for App Engine when a previously supported language runtime goes out of support by the upstream language community?

As for the famous Google App Engine price hike everyone likes to point to, the lower price was only at a pre-general availability launch stage.

You're right that they don't make any specific guarantees that they won't hike prices on short notice, but within the scope of Google Cloud Platform features that have already reached general availability, when have they done that?

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

#62

Post by inishchith » Sun, Dec 13, 2020, 4:23 PM UTC

nojvek wrote: post #48

Yesssss. Right now I have a cron that hits my app every minute to keep it warm. However even with that I see cold starts every now and then. This removed that problem. It’s so surprising that AWS and Azure don’t have an equivalent to GCP cloud run. Being able to run a container on demand with a custom image with whatever language and dependencies you want is amazing. I’ve spun up browsers for snapshotting and seeing…

Agree with most points made. Though interested to know where's your cron running? - is it one of your self-hosted servers or are you using some service for it like freshping.io?

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

#63

Post by nojvek » Sun, Dec 13, 2020, 8:59 PM UTC

inishchith wrote: post #62

nojvek wrote: post #48

Yesssss. Right now I have a cron that hits my app every minute to keep it warm. However even with that I see cold starts every now and then. This removed that problem. It’s so surprising that AWS and Azure don’t have an equivalent to GCP cloud run. Being able to run a container on demand with a custom image with whatever language and dependencies you want is amazing. I’ve spun up browsers for snapshotting and seeing…

Agree with most points made. Though interested to know where's your cron running? - is it one of your self-hosted servers or are you using some service for it like freshping.io?

Use google cloud scheduler for the cron. It’s the most expensive part of my stack at 15c/month.

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

#64

Post by nojvek » Sun, Dec 13, 2020, 9:01 PM UTC

digianarchist wrote: post #59

nojvek wrote: post #48

Yesssss. Right now I have a cron that hits my app every minute to keep it warm. However even with that I see cold starts every now and then. This removed that problem. It’s so surprising that AWS and Azure don’t have an equivalent to GCP cloud run. Being able to run a container on demand with a custom image with whatever language and dependencies you want is amazing. I’ve spun up browsers for snapshotting and seeing…

AWS added container support to Lambda recently.

It’s not the same as cloud run though. Cloud run just needs a thing listening on $PORT environment variable. That’s the only interface needed to the container. The rest is totally agnostic to knowing that it’s inside cloud run.

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

#65

Post by digianarchist » Mon, Dec 14, 2020, 11:34 PM UTC

nojvek wrote: post #64

digianarchist wrote: post #59

Earlier quoted context omitted.

AWS added container support to Lambda recently.

It’s not the same as cloud run though. Cloud run just needs a thing listening on $PORT environment variable. That’s the only interface needed to the container. The rest is totally agnostic to knowing that it’s inside cloud run.

Ah I see. So there's no need to write an interface that accepts the event object? It's all HTTP on Google Cloud Run?

Do you have to gracefully shutdown the container or does Google just kill the container once it gets a response?