Database connection pooling

[gopinathrimc]

Hi,

Currently i have a lambda function that is making a new connection to database on each invocation. This is causing downstream issues at the database level. Is there a way to pool connections? In the lambda best practices, there is a mention of db connections in the execution context reuse.
Now if i initialize a connection outside the lambda handler, how do i ensure that the connection is closed when execution environment is disposed of? issue #131 kind of touches on it, but not sure to how to ensure that the connections are closed safely.

[normj]

There is not a cleanup event when a Lambda compute environment is reclaimed. Are you seeing cases of your database thinking the connection is still open when the Lambda compute environment is reclaimed?

[normj]

Closing as there isn't much we can do now. The Lambda team is very keen on improving Database connection pooling experience.