[CSHARP-3176] Best practices for connection handling in AWS Lambda environment Created: 06/Aug/20  Updated: 14/Sep/20  Resolved: 14/Sep/20

Status: Closed
Project: C# Driver
Component/s: Connectivity, Documentation, Feature Request
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Trivial - P5
Reporter: Heshan Lokukarawita Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

AWS Lambda .NET Core



 Description   

Can anyone suggest best practices to use when developing AWS lambda functions (.NET core). Our main concern is MongoClient does not provide connection close method so this might leave too many opened connections and cluster might run into resource problems.

 



 Comments   
Comment by Esha Bhargava [ 14/Sep/20 ]

Hi there, thank you for reaching out. As this sounds like a support issue, I wanted to give you some resources to get this questioned answered more quickly:

  • our MongoDB support portal, located at support.mongodb.com
  • our MongoDB community portal, located here
    -If you are an Atlas customer, there is free support offered 24/7 in the lower right hand corner of the UI.
    Just in case you have already opened a support case and are not receiving sufficient help, please let me know and I can facilitate escalating your issue.
    Thank you!
Generated at Wed Feb 07 21:44:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.