News for hackers. Stuff that matters.
Re:Handling 350k Requests for $3 using Lambda by kenhwang on Friday February 28, 2020 @02:05PM (#22445353)
Seriously. Something like an AWS nano instance only costs $4/month and can easily handle that many requests an hour with a slow dynamic language.
Re:Handling 350k Requests for $3 using Lambda by jerf on Friday February 28, 2020 @02:13PM (#22445416)
The scary thing I saw is that while it's cool that Lambda is $2/month right now, which is negligible, it's $2/month for 900 users. If it scales linearly (and I don't know that it does, because I don't know exactly how the system works), then that means you're one good blog post somewhere about your extension away from being $200-$2000/month.

That said, my gut says there's a good chance that since the author is surprised at the rate of requests, there's almost certainly an optimization opportunity that wouldn't even take much effort.

Re:Handling 350k Requests for $3 using Lambda by tasogare on Friday February 28, 2020 @02:22PM (#22445505)
Especially the author has experience with docker so deploying a container for his app on Digital Ocean would be super quick and easy. In addition, the list of disadvantages seems longer than the advantages, with scary points like the difficulty to debug things (that could easily takes hours to figure out if something don’t run properly).
Re:Handling 350k Requests for $3 using Lambda by habosa on Friday February 28, 2020 @02:27PM (#22445552)
However in the case when they both get 0 requests, the Lambda solution costs $0 and the Micro instance still costs $4.

That's a really nice advantage for starting a new project where you're confident in unit economics but have unknown scale.

Re:Handling 350k Requests for $3 using Lambda by cnst on Friday February 28, 2020 @03:35PM (#22446088)
Is it two different arguments you're posting? How's $0 on zero requests is a better solution when the range would be 0 to $2000 for what's a fixed $4 without Lambda?

The $0 argument is also flowed because $4 is a fixed cost for unlimited $0 to $2000 solutions through hedging. If you have 10 solutions, what's the likelihood of all of them still doing $0, or at the very least below $4?

The unit economics argument is likewise hard to see in practice, because we'd be talking quite different numbers on a per-unit cost with Lambda vs. without, which may easily make the difference between making a profit or taking a loss, especially if it's a lifestyle business we're talking about.

Re:Handling 350k Requests for $3 using Lambda by abc-xyz on Friday February 28, 2020 @04:46PM (#22446723)
Pretty sure you'd have to pay at least $3.5 if you wanted to expose your Lambda function using AWS API Gateway (which I assume most would want to do).. The author mention $1.11 but that's for "HTTP APIs (Preview)" rather than "REST APIs" - in either case it wouldn't be 0. At least that's how I read it.. AWS pricing is such a mess with so many hidden fees (https://aws.amazon.com/api-gateway/pricing/)..
Re:Handling 350k Requests for $3 using Lambda by highfrequency on Friday February 28, 2020 @02:11PM (#22445405)
Is there no variable charge for network bandwidth?
Re:Handling 350k Requests for $3 using Lambda by kenhwang on Friday February 28, 2020 @03:00PM (#22445801)
Lambda and EC2 have the same network bandwidth charge.