Document best practice for managing MongoClient instances

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Won't Do
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I couldn't find best practice documentation for how to manage a MongoClient instance. Most examples just show it created by embedding it directly into a template. It's unclear whether in a real application one needs to worry about this, but I suspect that if it's done naively a new MongoClient could be created for every CRUD operation instead of one for all of them (assuming more than one is needed to process a single request.

            Assignee:
            Andreas Braun
            Reporter:
            Jeffrey Yemin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: