Azure Functions + Azure SQL + Node.js and connection pooling between requests?

Question

I wonder - is there a way to have an Azure SQL connection pool between Azure Functions (Node.js) requests?

Creating a connection is a significant chunk of the total time my requests are running and I wonder how to improve it.

All the examples on the tedious website http://tediousjs.github.io/tedious/getting-started.html open a new connection, while tedious-connection-pool https://github.com/tediousjs/tedious-connection-pool from what I can see is designed for using a single connection pool for a lifetime of a single request, not between requests.

Any suggestions are appreciated!

Matt Mason · Accepted Answer · 2017-04-05 17:40:25Z

3

I'd go the tedious-connection-pool route - it's designed to be used between requests.

Create the connection pool outside of your function scope:

// created only on first invocation
let pool = new ConnectionPool(poolConfig, connectionConfig);

module.exports = function(context, trigger) {
   // runs on every invocation, acquiring a connection from the pool
   pool.acquire((err, connection) => {
      ...
   });
}

answered Apr 5, 2017 at 17:40

Matt Mason

2,72411 silver badges22 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Azure Functions + Azure SQL + Node.js and connection pooling between requests?

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related