In Azure, instances of Node need to utilize outbound connections efficiently as there is a hard limit on the number of concurrent outbound ports (https://docs.microsoft.com/en-us/azure/load-balancer/troubleshoot-outbound-connection)
When profiling our use of outbound ports, we notice that mixpanel-node creates a very large number of connections since it is not leveraging connection pooling - this is causing us to exceed our SNAT thresholds and start failing requests. The library doesn't seem to support setting any configuration to override this behavior, any known workarounds?
In Azure, instances of Node need to utilize outbound connections efficiently as there is a hard limit on the number of concurrent outbound ports (https://docs.microsoft.com/en-us/azure/load-balancer/troubleshoot-outbound-connection)
When profiling our use of outbound ports, we notice that mixpanel-node creates a very large number of connections since it is not leveraging connection pooling - this is causing us to exceed our SNAT thresholds and start failing requests. The library doesn't seem to support setting any configuration to override this behavior, any known workarounds?