Bare ec2: 15ms
Lambda via API Gateway: 276ms
[0]: http://prerender.cloud/lambda-latency [1]: https://news.ycombinator.com/item?id=12678011
Bare ec2: 15ms
Lambda via API Gateway: 276ms
[0]: http://prerender.cloud/lambda-latency [1]: https://news.ycombinator.com/item?id=12678011
I understand that Lambdas are 'relatively quick' when they are 'hot' - which is my crude metaphor for 'up and running'.
The issue is, if the Lambda has not been in use for some time (seconds, minutes?), then the 'first call' can have quite a bit of latency - often up to 5 seconds - which killed it for us.
There is no way we could reasonably deploy a service wherein customer would have to wait an additional 5 seconds for a reaction in most use cases.
So close, yet so far.
This was about 18 months ago.
If you have some data that addresses this specific artifact - then that would be great. Possibly things have changed in 18 months.
And I'm not a hater, to us AWS is the best thing since sliced bread.
Lambda itself is fairly quick (~75ms), but API Gateway needs some work.
250ms we can live with for many things, but not 5x.
But yes - it should be under 50ms at all times I think for people to start taking it seriously.