ACS Node.js SDK connection pool default max sockets limit

Answer to the question

The ACS Node.js SDK does not publish a default maxSockets value. When the pool option is omitted, the SDK falls back to the default that Node’s http.Agent provides.

Confirmed facts

• Node 0.12+ http.Agent defaults to Infinity sockets per host.
• Node releases ≤0.10 used a hard‑coded default of 5 sockets.
• In Titanium SDK 7.5.0 GA the ACS client internally sets maxSockets to 5 when no pool configuration is supplied.

Undocumented / unsupported behavior

• The 5‑socket fallback seen in Titanium 7.5.0 is an internal implementation detail and is not documented as a supported default. Future SDK releases may change this behaviour.
• Pool semantics can shift when the underlying HTTP client library is upgraded, because newer versions may expose different defaults or configuration knobs.

Practical steps to verify your environment

1. Instantiate the ACS client without specifying a pool:

   const acs = require('acs-sdk');
   const client = new acs.Client({ /* credentials */ });
   console.log('maxSockets:', client.httpAgent.maxSockets);

2. Run a lightweight load test against an ACS endpoint while monitoring the number of concurrent TCP connections (e.g., netstat -an | grep ESTABLISHED on Linux).
3. Repeat the above steps across different Node.js versions and Titanium SDK releases to observe any changes in the default.

What to ask for clarification

If you plan to scale beyond the observed default, it is helpful to know the Node.js runtime version your application is using, as the default maxSockets differs between versions.