Improving API Response Times by Migrating from Cloud Functions to Cloud Run

Re:Improving API Response Times by Migrating from Cloud Func... by lysecret on Tuesday January 11, 2022 @08:53AM (#29891443)

hehe, im just going the other way for a startup of mine. Were i started with ECS (aws cloud run basically) and now going to lambda. Bot for our usecase the cold start isnt such a big deal.

[ Parent | on HN ]

Re:Improving API Response Times by Migrating from Cloud Func... by obcilion on Tuesday January 11, 2022 @09:08AM (#29891580)

If cold starts wasn't a problem we probably would have stayed with functions, and all of our non-api stuff is still on functions.

[ Parent | on HN ]

Re:Improving API Response Times by Migrating from Cloud Func... by lysecret on Tuesday January 11, 2022 @10:29AM (#29892597)

I wonder if the cold start will ever be fully fixed. Because most other services would seem to be made redundant then.

[ Parent | on HN ]

Re:Improving API Response Times by Migrating from Cloud Func... by jfbaro on Tuesday January 11, 2022 @11:23AM (#29893509)

It's getting better and better, and with a predictive ML model, it can become invisible for most use cases. Unfortunately, cloud Run has an even longer startup time if you need to span more "instances" in response to spikes in traffic, so Cloud Run doesn't fix the cold start yet.

[ Parent | on HN ]

Re:Improving API Response Times by Migrating from Cloud Func... by lysecret on Tuesday January 11, 2022 @12:16PM (#29894363)

good point. Also there is some competition with lambda like functions. So i hope it will get better and better:)

[ Parent | on HN ]