2

Let's assume I have one AWS lambda Function 

**String lambdaFunction1() {
//some processing 
}**

Let's say lambdaFunction1 is triggered on any new message in SNS Topic. How many JVM instances will be triggered for 10 SNS messages?

Does AWS lambda execute each lambda in it's own JVM or it re-utilizes same JVM instances.

JavaGeek_101
  • 41
  • 1
  • 5

1 Answers1

2

Quoting https://aws.amazon.com/de/blogs/compute/container-reuse-in-lambda/

Let’s say your function finishes, and some time passes, then you call it again. Lambda may create a new container all over again, in which case the experience is just as described above. This will be the case for certain if you change your code.

However, if you haven’t changed the code and not too much time has gone by, Lambda may reuse the previous container. This offers some performance advantages to both parties: Lambda gets to skip the nodejs language initialization, and you get to skip initialization in your code. Files that you wrote to /tmp last time around will still be there if the sandbox gets reused.

Remember, you can’t depend on a container being reused, since it’s Lambda’s prerogative to create a new one instead.

As said: You can not depend on the container being reused but there is a good chance when AWS deems it a performance gain.

Or to keep it simpler: AWS probably knows what to do to get your Lambdas as efficient as possible so you should not really overthink this probably.

Also while this blog is aimed at Node.js AWS seems to do something similar for Java based on this post by them.

Ben
  • 1,665
  • 1
  • 11
  • 22
  • And on of the key takeaways is that your lambda must not keep state, neither in memory nor on disk since otherwise repeated executions on the same instance will get you into trouble. – luk2302 Mar 01 '18 at 09:22
  • Ok, that means each lambda instance is one container. thanks for insight – JavaGeek_101 Mar 01 '18 at 09:22