3 ms·
Is this addressing any of the cold start problems? One of the things that attracts me to Serverless is not paying anything (or vey little) until a project is p
by jonplackett 8y ago
Is this addressing any of the cold start problems?
One of the things that attracts me to Serverless is not paying anything (or vey little) until a project is properly off the ground.
But with things like Heroku there’s a ridiculous delay to start up if here hasn’t been a request for a while.
Does Serverless / this implementation of Serverless address that at all?
- matteuan 8y agoI can confirm AWS Lambda still has this problem. A dirty solution could be to time-trigger your function every x seconds to keep the container alive. For example, doing that every 10 seconds would produce 259200 request per 30-days month, so 0,05 USD per month for this in AWS.
- jonplackett 8y agoSmart! Kinda silly that it's required, but a good and super-cheap solution. Thanks.
- nicoburns 8y ago> One of the things that attracts me to Serverless is not paying anything (or vey little) until a project is properly off the ground. I guess it's not quite nothing, but can't you just buy a cheap $5 (or even $2.50) VM, and run all of your small projects off of the same one. The cost is pretty small, and you don't have to worry about how your going to migrate your code off the serverless platform later.
- jonplackett 8y agoYeah that's basically what I do now. Amazon's Lightsail is really good for this. What I'd really like though is one place I can just put the code, test it and know I can leave it there when it gets bigger. That's the dream anyway, but I guess nothing's perfect!