3 ms·
I write a lot of Java on AWS lambda and love it for a lot of use cases. You manage dependencies by bundling them up in a JAR or zip file (handled by Maven or G
by RhodesianHunter 10y ago
I write a lot of Java on AWS lambda and love it for a lot of use cases.
You manage dependencies by bundling them up in a JAR or zip file (handled by Maven or Gradle)
Static assets can be kept warm between invocations (nice for things like DB connections)
- lars_francke 10y agoPerfect, thank you. Some of the docs I read made it out so that instances of my functions would never be reused. Or to put it better: I should not rely on them being reused. If I keep DB connections for example am I now relying on an implementation detail or is this documented behavior? I realize that this will be different for every system.
- RhodesianHunter 10y agoAs long as you invoke your lambda again within a few minutes it will re-use your static assets. I'm sure they use your invocation history in deciding how long to keep them around.