Best practices for connection handling in AWS Lambda environment

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Trivial - P5
    • None
    • Affects Version/s: None
    • Component/s: Connectivity, Documentation, Feature Request
    • None
    • Environment:
      AWS Lambda .NET Core
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

       

              Assignee:
              Unassigned
              Reporter:
              Heshan Lokukarawita
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: