Reusing Database Connections With Azure Functions Using Javascript





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I cannot find clear information on how to manage database connections (MongoDB in my case) from an Azure function written in Javascript.



The Microsoft document below says to not create a connection for each invocation of the function by using static variables in C# using .NET Framework Data Provider for SQL Server and the pooling is handled by the client connection. It does not describe how to do this in Javascript.



https://docs.microsoft.com/en-us/azure/azure-functions/manage-connections



A solution of creating a global variable to hold the database client between invocations is described here but the author is not confident this is the correct way to do it.



http://thecodebarbarian.com/getting-started-with-azure-functions-and-mongodb.html



Has anyone used this in production or understand if this is the correct approach?










share|improve this question























  • Refer to MongoClient Connection Pooling section here and use similar pattern in your Azure Function. mongodb.github.io/node-mongodb-native/driver-articles/…

    – Baskar
    Nov 22 '18 at 4:37


















0















I cannot find clear information on how to manage database connections (MongoDB in my case) from an Azure function written in Javascript.



The Microsoft document below says to not create a connection for each invocation of the function by using static variables in C# using .NET Framework Data Provider for SQL Server and the pooling is handled by the client connection. It does not describe how to do this in Javascript.



https://docs.microsoft.com/en-us/azure/azure-functions/manage-connections



A solution of creating a global variable to hold the database client between invocations is described here but the author is not confident this is the correct way to do it.



http://thecodebarbarian.com/getting-started-with-azure-functions-and-mongodb.html



Has anyone used this in production or understand if this is the correct approach?










share|improve this question























  • Refer to MongoClient Connection Pooling section here and use similar pattern in your Azure Function. mongodb.github.io/node-mongodb-native/driver-articles/…

    – Baskar
    Nov 22 '18 at 4:37














0












0








0








I cannot find clear information on how to manage database connections (MongoDB in my case) from an Azure function written in Javascript.



The Microsoft document below says to not create a connection for each invocation of the function by using static variables in C# using .NET Framework Data Provider for SQL Server and the pooling is handled by the client connection. It does not describe how to do this in Javascript.



https://docs.microsoft.com/en-us/azure/azure-functions/manage-connections



A solution of creating a global variable to hold the database client between invocations is described here but the author is not confident this is the correct way to do it.



http://thecodebarbarian.com/getting-started-with-azure-functions-and-mongodb.html



Has anyone used this in production or understand if this is the correct approach?










share|improve this question














I cannot find clear information on how to manage database connections (MongoDB in my case) from an Azure function written in Javascript.



The Microsoft document below says to not create a connection for each invocation of the function by using static variables in C# using .NET Framework Data Provider for SQL Server and the pooling is handled by the client connection. It does not describe how to do this in Javascript.



https://docs.microsoft.com/en-us/azure/azure-functions/manage-connections



A solution of creating a global variable to hold the database client between invocations is described here but the author is not confident this is the correct way to do it.



http://thecodebarbarian.com/getting-started-with-azure-functions-and-mongodb.html



Has anyone used this in production or understand if this is the correct approach?







javascript mongodb mongoose azure-functions






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 0:21









Hamish AndersonHamish Anderson

104




104













  • Refer to MongoClient Connection Pooling section here and use similar pattern in your Azure Function. mongodb.github.io/node-mongodb-native/driver-articles/…

    – Baskar
    Nov 22 '18 at 4:37



















  • Refer to MongoClient Connection Pooling section here and use similar pattern in your Azure Function. mongodb.github.io/node-mongodb-native/driver-articles/…

    – Baskar
    Nov 22 '18 at 4:37

















Refer to MongoClient Connection Pooling section here and use similar pattern in your Azure Function. mongodb.github.io/node-mongodb-native/driver-articles/…

– Baskar
Nov 22 '18 at 4:37





Refer to MongoClient Connection Pooling section here and use similar pattern in your Azure Function. mongodb.github.io/node-mongodb-native/driver-articles/…

– Baskar
Nov 22 '18 at 4:37












1 Answer
1






active

oldest

votes


















1














Yes, there's a very close equivalence between C#/SQL storing a single SqlConnection instance in a static variable and JS/MongoDB storing a single Db instance in a global variable. The basic pattern for JS/MongoDB in Azure Functions is (assuming you're up to date for async/await - alternatively you can use callbacks as per your linked article):



// getDb.js

let dbInstance;

module.exports = async function() {
if (!dbInstance) {
dbInstance = await MongoClient.connect(uri);
}
return dbInstance;
};

// function.js

const getDb = require('./getDb.js');

module.exports = async function(context, trigger) {
let db = await getDb();
// ... do stuff with db ..
};


This will mean you only instantiate one Db object per host instance. Note this isn't one per Function App - if you're using a dedicated App Service Plan then there will be the number of instances you've specified in the plan, and if you're using a Consumption Plan then it'll vary depending on how busy your app is.






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422257%2freusing-database-connections-with-azure-functions-using-javascript%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    Yes, there's a very close equivalence between C#/SQL storing a single SqlConnection instance in a static variable and JS/MongoDB storing a single Db instance in a global variable. The basic pattern for JS/MongoDB in Azure Functions is (assuming you're up to date for async/await - alternatively you can use callbacks as per your linked article):



    // getDb.js

    let dbInstance;

    module.exports = async function() {
    if (!dbInstance) {
    dbInstance = await MongoClient.connect(uri);
    }
    return dbInstance;
    };

    // function.js

    const getDb = require('./getDb.js');

    module.exports = async function(context, trigger) {
    let db = await getDb();
    // ... do stuff with db ..
    };


    This will mean you only instantiate one Db object per host instance. Note this isn't one per Function App - if you're using a dedicated App Service Plan then there will be the number of instances you've specified in the plan, and if you're using a Consumption Plan then it'll vary depending on how busy your app is.






    share|improve this answer




























      1














      Yes, there's a very close equivalence between C#/SQL storing a single SqlConnection instance in a static variable and JS/MongoDB storing a single Db instance in a global variable. The basic pattern for JS/MongoDB in Azure Functions is (assuming you're up to date for async/await - alternatively you can use callbacks as per your linked article):



      // getDb.js

      let dbInstance;

      module.exports = async function() {
      if (!dbInstance) {
      dbInstance = await MongoClient.connect(uri);
      }
      return dbInstance;
      };

      // function.js

      const getDb = require('./getDb.js');

      module.exports = async function(context, trigger) {
      let db = await getDb();
      // ... do stuff with db ..
      };


      This will mean you only instantiate one Db object per host instance. Note this isn't one per Function App - if you're using a dedicated App Service Plan then there will be the number of instances you've specified in the plan, and if you're using a Consumption Plan then it'll vary depending on how busy your app is.






      share|improve this answer


























        1












        1








        1







        Yes, there's a very close equivalence between C#/SQL storing a single SqlConnection instance in a static variable and JS/MongoDB storing a single Db instance in a global variable. The basic pattern for JS/MongoDB in Azure Functions is (assuming you're up to date for async/await - alternatively you can use callbacks as per your linked article):



        // getDb.js

        let dbInstance;

        module.exports = async function() {
        if (!dbInstance) {
        dbInstance = await MongoClient.connect(uri);
        }
        return dbInstance;
        };

        // function.js

        const getDb = require('./getDb.js');

        module.exports = async function(context, trigger) {
        let db = await getDb();
        // ... do stuff with db ..
        };


        This will mean you only instantiate one Db object per host instance. Note this isn't one per Function App - if you're using a dedicated App Service Plan then there will be the number of instances you've specified in the plan, and if you're using a Consumption Plan then it'll vary depending on how busy your app is.






        share|improve this answer













        Yes, there's a very close equivalence between C#/SQL storing a single SqlConnection instance in a static variable and JS/MongoDB storing a single Db instance in a global variable. The basic pattern for JS/MongoDB in Azure Functions is (assuming you're up to date for async/await - alternatively you can use callbacks as per your linked article):



        // getDb.js

        let dbInstance;

        module.exports = async function() {
        if (!dbInstance) {
        dbInstance = await MongoClient.connect(uri);
        }
        return dbInstance;
        };

        // function.js

        const getDb = require('./getDb.js');

        module.exports = async function(context, trigger) {
        let db = await getDb();
        // ... do stuff with db ..
        };


        This will mean you only instantiate one Db object per host instance. Note this isn't one per Function App - if you're using a dedicated App Service Plan then there will be the number of instances you've specified in the plan, and if you're using a Consumption Plan then it'll vary depending on how busy your app is.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 22 '18 at 14:49









        MarkXAMarkXA

        3,1211215




        3,1211215
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422257%2freusing-database-connections-with-azure-functions-using-javascript%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            鏡平學校

            ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

            Why https connections are so slow when debugging (stepping over) in Java?