Hacker News new | ask | show | jobs
by risaacs99 3088 days ago
This is just not true. A brand new account on AWS will come with a default lambda limit of 1000 concurrent invocations with up to 2 cores and 3gb per invocation. That is a massive amount of computing power. The load balancer (typically API gateway in front of lambda for a serverless app) will scale very quickly to any request volume and no one needs to be notified ahead of time.
2 comments
thezilch 3088 days ago
We have different meanings for "massive surges" and "massive amount of computing power" and "very quickly". I personally have stake in AWS/EC2 performance -- see profile -- and have actual experience in these limits. It's nothing against AWS -- again, I'm still spending with them -- as elastic compute, networking, storage, etc is not easy, but the limitations are very absolute and not "massive" nor "quick" in the article's "world changing" sense.
link
always_good 3088 days ago
AWS' Elastic Load Balancer took minutes to spin up such that it was pretty useless, god forbid you're getting DoSed.

I have a hard time believing that their other products don't have the same issue when auto-scaling.

link
thezilch 3088 days ago
Lambda is backed by EC2 and absolutely has EC2's limits. Just like scaling an ELB takes minutes to serve "massive surges" -- AWS recommends you pre-warm ELBs or contact them to do so -- the same is true of Lambda.
link
risaacs99 3087 days ago
AWS no longer recommends warming up the newer ALBs for the vast majority of customers and scenarios. Of course lambda isn't magic and has an initial start penalty. There are ways to mitigate it and as long as you are actively handling requests your functions will be reused. It's not magic, but it's capable of keeping up with normal traffic surges. If you have a special circumstance where you expect a large surge on a scheduled basis (say thousands of clients checking in at the stroke of midnight, you would have to arrange to be ready for that and there are a lot of ways to do it).

API gateway isn't alb or elb and there isn't any recommendation or expectation that customers warm anything up.

I never said "massive surge" but I stand by the idea that 2000 cores and 6 terabytes of memory is massive for most workloads. Of course, that's not the limit and you can request more if you need it.

Lambda isn't for all workloads but AWS (and everyone else) is always changing and improving. You have to check in occasionally to see if old assumptions (e.g. elb) still hold.

link