best practice for Lambda DB connection - Githubissues

winglang / wing

A programming language for the cloud ☁️ A unified programming model, combining infrastructure and runtime code into one language ⚡

https://winglang.io

Other

4.8k stars 189 forks source link

best practice for Lambda DB connection #5529

Open ekeren opened 6 months ago

ekeren commented 6 months ago

Use Case

It is now possible to implement the best practice described by atlas here

Including:

Define the client to the MongoDB server outside the AWS Lambda handler function. - Reusing the same mongodb connection for warm lambda (preventing exhausting sockets in machine)
Setting callbackWaitsForEmptyEventLoop to false
Review https://www.mongodb.com/docs/atlas/manage-connections-aws-lambda/ for more

Proposed Solution

No response

Implementation Notes

No response

Component

SDK

Community Notes

Please vote by adding a 👍 reaction to the issue to help us prioritize.
If you are interested to work on this issue, please leave a comment.
If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out on the #dev channel in the Wing Slack.

marciocadev commented 6 months ago

Hey @ekeren ,

The same concept can be applied to all resources in AWS (SQS, SNS, DynamoDB, etc).

Define the client outside the handler to instantiate only during container loading and reuse it for each execution.