News for hackers. Stuff that matters.
Re:The hidden costs of serverless by bluepeter on Wednesday January 17, 2018 @10:28PM (#16174443)
> Cold starts. This isn’t the time to dive in deep, but it’s a main reason why some companies decided against going Serverless.

Cold starts as an issue? I mean, all you have to do is create a CloudWatch event (or cron if you want an explicit server involved) to fire the Lambda function every few minutes and you're all good. Sure, if you get heavy traffic, I suppose you could have multiple containers running simultaneously? But that's also easy enough to handle w/ CW events.

Re:The hidden costs of serverless by mslate on Wednesday January 17, 2018 @10:44PM (#16174514)
Wow, sounds easy--almost as if it should be that way out of the box...
Re:The hidden costs of serverless by dasil003 on Wednesday January 17, 2018 @11:02PM (#16174600)
The economics don't work out if they keep them all hot all the time.
Re:The hidden costs of serverless by hliyan on Wednesday January 17, 2018 @11:05PM (#16174608)
Woot can't they give a simple Boolean seeing for a slightly higher price: "always up"?
Re:The hidden costs of serverless by bluepeter on Wednesday January 17, 2018 @11:18PM (#16174660)
It's probably not as easy as that. Lambda functions run in a container. If you have a spike in traffic, you may have 10 different containers handling requests. So should they keep 1 container always up, or 3, or 10. I suppose you could have some ELB-type rules to "auto-scale" new containers...
Re:The hidden costs of serverless by hliyan on Wednesday January 17, 2018 @11:07PM (#16174617)
*why can't they

My mobile client's edit doesn't work

Re:The hidden costs of serverless by bluepeter on Wednesday January 17, 2018 @11:13PM (#16174644)
They do for me. It's basically free to fire a function every 5 minutes, have the function immediately close, and have that Lambda container sit around for another ~10 minutes "hot" and waiting for a real request to handle.
Re:The hidden costs of serverless by chrisan on Thursday January 18, 2018 @05:50AM (#16176128)
Aren't these cloudwatch/cron events basically doing exactly that? People are keeping their functions hot and not using resources but AWS is having to keep those containers up 100% of the time
Re:The hidden costs of serverless by dasil003 on Thursday January 18, 2018 @03:16PM (#16180927)
Yes, but by making it something you have to laboriously set up rather than a default 95% of people won't do it, and you can afford to let 5% do this hack without jacking up low-end prices.
Re:The hidden costs of serverless by herbturbo on Thursday January 18, 2018 @12:11PM (#16178803)
One of the big problems with Lambda cold starts is the concurrency issue, especially if your Lambdas are running inside a VPC: https://hackernoon.com/im-afraid-you-re-thinking-about-aws-l...
Re:The hidden costs of serverless by noway421 on Thursday January 18, 2018 @06:18AM (#16176252)
That sounds like a hack, not a working solution
Re:The hidden costs of serverless by jrs95 on Wednesday January 17, 2018 @10:34PM (#16174473)
At that point, if you’re running it all the time anyways, why not just have something like an auto scaling Kubernetes cluster?
Re:The hidden costs of serverless by CharlesW on Wednesday January 17, 2018 @10:46PM (#16174525)
Because the cost and level-of-effort difference between those two options isn't comparable. Firing a function in a way that keeps it awake but uses no perceptible resources is simple and basically free.
Re:The hidden costs of serverless by jrs95 on Wednesday January 17, 2018 @10:49PM (#16174544)
I wasn’t super familiar with the pricing, this makes sense.