Using DocumentDB with Lambda: connection pooling

Question

I would like to implement a modern web app with serverless compute using AWS Lambda and Amazon DocumentDB. How can I manage efficiently connections to the DB? Is there a connection pool mechanism, like the one you have when using Amazon RDS Proxy, to avoid opening and closing connections from every Lambda execution?

Thanks a lot!

[1]: https://aws.amazon.com/blogs/compute/using-amazon-rds-proxy-with-aws-lambda/

Accepted Answer

Best practices are similar to what you would do when connecting to another data store: declare the variable holding the connection to the database outside your handler so it can be re-utilized by subsequent invocations of your function.

You can find a good example here: https://docs.atlas.mongodb.com/best-practices-connecting-to-aws-lambda.

Using DocumentDB with Lambda: connection pooling

Relevant content