Re:AWS Lambda Makes Serverless Applications a Reality
by imglorp on Tuesday November 24, 2015 @07:02PM
(#10624497)
Our issue was price. Boss did the math for our use case, around a million hits/sec 24/7, and it worked out to billions of dollars. We're building a solution (on aws) for a little less than that.
Re:AWS Lambda Makes Serverless Applications a Reality
by x5n1 on Wednesday November 25, 2015 @02:27AM
(#10625869)
It's good the boss can do that sort of math. That's why you need him and why he is called the boss.
Re:AWS Lambda Makes Serverless Applications a Reality
by eistrati on Wednesday November 25, 2015 @08:34AM
(#10627066)
Why do I have a feeling that you are the "boss" in this picture? :)
Re:AWS Lambda Makes Serverless Applications a Reality
by toomuchtodo on Tuesday November 24, 2015 @05:23PM
(#10623997)
You could use a scheduled cron task in Lambda to make requests to keep your API hot.
Re:AWS Lambda Makes Serverless Applications a Reality
by posabsolute on Tuesday November 24, 2015 @05:27PM
(#10624018)
Yeah we thought about that, but is it reliable? We were really not sure we could always get rid of the cold start issue.
Re:AWS Lambda Makes Serverless Applications a Reality
by twagner on Tuesday November 24, 2015 @06:47PM
(#10624421)
AWS Lambda function schedules are driven off the same fault-tolerant, highly available service that powers SWF. (So...yes, they're reliable :)
Re:AWS Lambda Makes Serverless Applications a Reality
by anonymoushn on Tuesday November 24, 2015 @07:05PM
(#10624509)
Is keeping it hot with a cron job reliable though?
Re:AWS Lambda Makes Serverless Applications a Reality
by toadkicker on Tuesday November 24, 2015 @06:16PM
(#10624282)
Give SNS/SQS a look for polling solutions for API Gateway. We got around it by having a health check call in our set up.
Re:AWS Lambda Makes Serverless Applications a Reality
by beefsack on Tuesday November 24, 2015 @06:20PM
(#10624296)
You could potentially use that task as an availability test too.
Re:AWS Lambda Makes Serverless Applications a Reality
by CodeWriter23 on Tuesday November 24, 2015 @07:47PM
(#10624662)
There's the performance issue on startup, then there's the cost issue with the typical case. With the "round up to the nearest 100ms" pricing, your example ends up overpaying 20-50% for the _typical_ case. If you have any serious use of your app, you are better off with DIY on EC2 or using Heroku.
It's awesome!.. Until you have to deal with the cold start issue. Our first call takes about 1.5 seconds; and then all other calls take about 50-80ms.
Your container stays in cache about 5-10 minutes unless it is called back, there are no guarantees.
This micro service is not called often and for us 1.5 seconds is never acceptable.