3 ms·
The most impressive thing (for us) that you could do with AWS Lambda is easily scale your functions without being worried about scaling. For example, we [1] ha
by artembugara 6y ago
The most impressive thing (for us) that you could do with AWS Lambda is easily scale your functions without being worried about scaling.
For example, we [1] have an API that runs Lambda functions to extract the structured content out of the news article. At some point, we have very few new articles being discovered by our system (night time in the US, for example). Other time, there are ~100 new articles every second. And, we do not have to worry about our infrastructure: 100 Lambdas will be executed concurrently, and we'll pay for just 100 Lambdas like if they were one after one.
Also, for many startups/side-projects when you don't know what would be your workload in advance, Lambda can save you money. And, if you somehow have a huge workload your solution won't be crashing.
[1] https://newscatcherapi.com/ https://newscatcherapi.com/
- maerF0x0 6y ago> without being worried about scaling So long as your RPS is low enough and you fit into the fairly tight APIGw+ Lambda edge cases box. https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html https://docs.aws.amazon.com/apigateway/latest/developerguide...
- davidgf 6y agoLambda scales well... until it does not. If your traffic pattern is very spiky and unpredictable, the burst limit can be a real pain in the neck. It ranges between 500 and 3.000 Lambda instances, depending on the region, and when that threshold is reached it can only spin up 500 more each minute. This is sufficient in most cases, indeed, but it's important to be aware of the implications of this limitation before believing that you can throw anything at Lambda and it'll just scale up to accommodate any workload.