Nodejs with persistent connection (MySQL/Redis)










0















I wonder what is the optimal way to establish/maintain connection with MySQL/Redis (from nodejs): store in one single object (conn) or create a new connection on every request? Namely:



1, Should we use a single connection for every nodejs http request? Use connection pool? Or a single connection on every new request (so reconnection should be important because the connection could be randomly lost)? How is the performance?



2, What is the difference between MySQL and Redis in term of maintaining such connection?










share|improve this question




























    0















    I wonder what is the optimal way to establish/maintain connection with MySQL/Redis (from nodejs): store in one single object (conn) or create a new connection on every request? Namely:



    1, Should we use a single connection for every nodejs http request? Use connection pool? Or a single connection on every new request (so reconnection should be important because the connection could be randomly lost)? How is the performance?



    2, What is the difference between MySQL and Redis in term of maintaining such connection?










    share|improve this question


























      0












      0








      0


      2






      I wonder what is the optimal way to establish/maintain connection with MySQL/Redis (from nodejs): store in one single object (conn) or create a new connection on every request? Namely:



      1, Should we use a single connection for every nodejs http request? Use connection pool? Or a single connection on every new request (so reconnection should be important because the connection could be randomly lost)? How is the performance?



      2, What is the difference between MySQL and Redis in term of maintaining such connection?










      share|improve this question
















      I wonder what is the optimal way to establish/maintain connection with MySQL/Redis (from nodejs): store in one single object (conn) or create a new connection on every request? Namely:



      1, Should we use a single connection for every nodejs http request? Use connection pool? Or a single connection on every new request (so reconnection should be important because the connection could be randomly lost)? How is the performance?



      2, What is the difference between MySQL and Redis in term of maintaining such connection?







      mysql node.js database redis






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 15 '18 at 2:19







      hiro

















      asked Nov 15 '18 at 1:49









      hirohiro

      76217




      76217






















          1 Answer
          1






          active

          oldest

          votes


















          0














          I will tell you how I used to manage to do this.




          1, Should we use a single connection for every nodejs http request? Use connection pool? Or a single connection on every new request (so reconnection should be important because the connection could be randomly lost)? How is the performance?




          You don't want to create connections manually for every nodejs http request. Always use connection pooling if you are using nodejs mysqlijs/mysql module. I use it.



          Pools take care of server reconnections automatically.



          I don't have a benchmarks, but performance should be better because within pools connections can be reused once released. In other factors, believe me, creating and managing connections manually is cumbersome and error-prone.



          Eg:
          Declare your mysql connection pool in a Db.js file like below and export it.



          var mysql = require("mysql");
          var pool = mysql.createPool( 'localhost',
          user : process.env.DB_USER,
          password : process.env.DB_PASSWORD,
          database : 'mydb'
          );

          module.exports = db;


          And use it in your inside an end-point in another file.



          var pool = require('./Db.js');

          app.get('/endpoint', function (req, res)
          // ...
          pool.query('<your-query-here>', function (err, res, fields)
          if (err) throw err;
          // do something with result (res)
          );

          );


          I prefer using both pool.query and pool.getConnection based on the scenario. Using query is safer because you don't need to consider releasing connection. It will be automatically handled by the library. getConnection is used only where several queries has to be run inside an end-point, so I can reuse the same connection to do that.




          2, What is the difference between MySQL and Redis in term of maintaining such connection?




          In short, You don't need pooling for redis. We don't think about pooling redis connections according to this.






          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%2f53311312%2fnodejs-with-persistent-connection-mysql-redis%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









            0














            I will tell you how I used to manage to do this.




            1, Should we use a single connection for every nodejs http request? Use connection pool? Or a single connection on every new request (so reconnection should be important because the connection could be randomly lost)? How is the performance?




            You don't want to create connections manually for every nodejs http request. Always use connection pooling if you are using nodejs mysqlijs/mysql module. I use it.



            Pools take care of server reconnections automatically.



            I don't have a benchmarks, but performance should be better because within pools connections can be reused once released. In other factors, believe me, creating and managing connections manually is cumbersome and error-prone.



            Eg:
            Declare your mysql connection pool in a Db.js file like below and export it.



            var mysql = require("mysql");
            var pool = mysql.createPool( 'localhost',
            user : process.env.DB_USER,
            password : process.env.DB_PASSWORD,
            database : 'mydb'
            );

            module.exports = db;


            And use it in your inside an end-point in another file.



            var pool = require('./Db.js');

            app.get('/endpoint', function (req, res)
            // ...
            pool.query('<your-query-here>', function (err, res, fields)
            if (err) throw err;
            // do something with result (res)
            );

            );


            I prefer using both pool.query and pool.getConnection based on the scenario. Using query is safer because you don't need to consider releasing connection. It will be automatically handled by the library. getConnection is used only where several queries has to be run inside an end-point, so I can reuse the same connection to do that.




            2, What is the difference between MySQL and Redis in term of maintaining such connection?




            In short, You don't need pooling for redis. We don't think about pooling redis connections according to this.






            share|improve this answer



























              0














              I will tell you how I used to manage to do this.




              1, Should we use a single connection for every nodejs http request? Use connection pool? Or a single connection on every new request (so reconnection should be important because the connection could be randomly lost)? How is the performance?




              You don't want to create connections manually for every nodejs http request. Always use connection pooling if you are using nodejs mysqlijs/mysql module. I use it.



              Pools take care of server reconnections automatically.



              I don't have a benchmarks, but performance should be better because within pools connections can be reused once released. In other factors, believe me, creating and managing connections manually is cumbersome and error-prone.



              Eg:
              Declare your mysql connection pool in a Db.js file like below and export it.



              var mysql = require("mysql");
              var pool = mysql.createPool( 'localhost',
              user : process.env.DB_USER,
              password : process.env.DB_PASSWORD,
              database : 'mydb'
              );

              module.exports = db;


              And use it in your inside an end-point in another file.



              var pool = require('./Db.js');

              app.get('/endpoint', function (req, res)
              // ...
              pool.query('<your-query-here>', function (err, res, fields)
              if (err) throw err;
              // do something with result (res)
              );

              );


              I prefer using both pool.query and pool.getConnection based on the scenario. Using query is safer because you don't need to consider releasing connection. It will be automatically handled by the library. getConnection is used only where several queries has to be run inside an end-point, so I can reuse the same connection to do that.




              2, What is the difference between MySQL and Redis in term of maintaining such connection?




              In short, You don't need pooling for redis. We don't think about pooling redis connections according to this.






              share|improve this answer

























                0












                0








                0







                I will tell you how I used to manage to do this.




                1, Should we use a single connection for every nodejs http request? Use connection pool? Or a single connection on every new request (so reconnection should be important because the connection could be randomly lost)? How is the performance?




                You don't want to create connections manually for every nodejs http request. Always use connection pooling if you are using nodejs mysqlijs/mysql module. I use it.



                Pools take care of server reconnections automatically.



                I don't have a benchmarks, but performance should be better because within pools connections can be reused once released. In other factors, believe me, creating and managing connections manually is cumbersome and error-prone.



                Eg:
                Declare your mysql connection pool in a Db.js file like below and export it.



                var mysql = require("mysql");
                var pool = mysql.createPool( 'localhost',
                user : process.env.DB_USER,
                password : process.env.DB_PASSWORD,
                database : 'mydb'
                );

                module.exports = db;


                And use it in your inside an end-point in another file.



                var pool = require('./Db.js');

                app.get('/endpoint', function (req, res)
                // ...
                pool.query('<your-query-here>', function (err, res, fields)
                if (err) throw err;
                // do something with result (res)
                );

                );


                I prefer using both pool.query and pool.getConnection based on the scenario. Using query is safer because you don't need to consider releasing connection. It will be automatically handled by the library. getConnection is used only where several queries has to be run inside an end-point, so I can reuse the same connection to do that.




                2, What is the difference between MySQL and Redis in term of maintaining such connection?




                In short, You don't need pooling for redis. We don't think about pooling redis connections according to this.






                share|improve this answer













                I will tell you how I used to manage to do this.




                1, Should we use a single connection for every nodejs http request? Use connection pool? Or a single connection on every new request (so reconnection should be important because the connection could be randomly lost)? How is the performance?




                You don't want to create connections manually for every nodejs http request. Always use connection pooling if you are using nodejs mysqlijs/mysql module. I use it.



                Pools take care of server reconnections automatically.



                I don't have a benchmarks, but performance should be better because within pools connections can be reused once released. In other factors, believe me, creating and managing connections manually is cumbersome and error-prone.



                Eg:
                Declare your mysql connection pool in a Db.js file like below and export it.



                var mysql = require("mysql");
                var pool = mysql.createPool( 'localhost',
                user : process.env.DB_USER,
                password : process.env.DB_PASSWORD,
                database : 'mydb'
                );

                module.exports = db;


                And use it in your inside an end-point in another file.



                var pool = require('./Db.js');

                app.get('/endpoint', function (req, res)
                // ...
                pool.query('<your-query-here>', function (err, res, fields)
                if (err) throw err;
                // do something with result (res)
                );

                );


                I prefer using both pool.query and pool.getConnection based on the scenario. Using query is safer because you don't need to consider releasing connection. It will be automatically handled by the library. getConnection is used only where several queries has to be run inside an end-point, so I can reuse the same connection to do that.




                2, What is the difference between MySQL and Redis in term of maintaining such connection?




                In short, You don't need pooling for redis. We don't think about pooling redis connections according to this.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 15 '18 at 4:52









                isuru89isuru89

                493513




                493513





























                    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%2f53311312%2fnodejs-with-persistent-connection-mysql-redis%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

                    Top Tejano songwriter Luis Silva dead of heart attack at 64

                    ReactJS Fetched API data displays live - need Data displayed static

                    政党