You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that my database is being 'connected' with every call to my function. My understanding from reading this AWS article is that any code outside of the specified handler functions, or the 'Execution Context', is maintained in anticipation of further invocations of the function.
Is the behaviour simulated at all in serverless-offline?
The text was updated successfully, but these errors were encountered:
No, this isn't an exact simulation of the lambda environment. The concept of container reuse for example isn't applicable with serverless-offline; the code for your lambda is re-executed with every request.
Ah okay great - I was just looking for confirmation that there wasn't a flaw in my code causing the re-execution, as it would have caused problems in production, but is okay for development I think.
I've noticed that my database is being 'connected' with every call to my function. My understanding from reading this AWS article is that any code outside of the specified handler functions, or the 'Execution Context', is maintained in anticipation of further invocations of the function.
Is the behaviour simulated at all in serverless-offline?
The text was updated successfully, but these errors were encountered: