You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really sure where to ask this, but I have an express server that makes two types of outgoing connections to various hosts. One type is handled by a 3rd party library where we cannot set an agent. The other is controlled by us where we can set an agent and pool the connections. I've been unable to find any guidance on pooling some connections but not all. Doesn't seem like the best case scenario, but not sure if it's something to be completely avoided? Unfortunately, Azure has put us in a spot where we need to get some connections pooled or scale out, so trying to figure out implications. Thanks for any guidance.
The text was updated successfully, but these errors were encountered:
I landed on this repo from the MSFT Azure docs here: https://docs.microsoft.com/en-us/azure/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide
Not really sure where to ask this, but I have an express server that makes two types of outgoing connections to various hosts. One type is handled by a 3rd party library where we cannot set an agent. The other is controlled by us where we can set an agent and pool the connections. I've been unable to find any guidance on pooling some connections but not all. Doesn't seem like the best case scenario, but not sure if it's something to be completely avoided? Unfortunately, Azure has put us in a spot where we need to get some connections pooled or scale out, so trying to figure out implications. Thanks for any guidance.
The text was updated successfully, but these errors were encountered: