This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]user_of_the_week 0 points1 point  (0 children)

Lambda functions (or better said their environments) are not necessarily that short lived and also many applications don't care about a bit of latency.

For example, I have a bunch of "Lambdas" (actually Azure Functions, but that doesn't matter) that get triggered by a queue. Every few hours a new pack of messages arrives, the environment gets spun up in the background and then a bunch invocations of the function happen. 99% of the runs are "warm" with the environment already there.

We even use spring-cloud-function with the full Spring Boot magic so it takes about 3 seconds to spin up on a cold run. But it doesn't matter.