Implement connection queueing to avoid nodejs connection limits

I sometimes get this error after doing some requests:

{ [Error: getaddrinfo ENOTFOUND www.googleapis.com www.googleapis.com:443]
  code: 'ENOTFOUND',
  errno: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'www.googleapis.com',
  host: 'www.googleapis.com',
  port: 443 }

Here is the last request I’m recording:

{ url: 'https://www.googleapis.com/youtube/v3/channels',
  method: 'GET',
  json: true,
  qs: { part: 'id, contentDetails', id: 'UChu4DxadETMAMlgwBREcNvQ' },
  useQuerystring: true,
  headers: { Authorization: 'Bearer mytoken' } }

[JustinBeckwith]

Greetings folks! I’d love to do something here, but with hundreds of API endpoints, it’s hard to come up with a unified queuing strategy that’s going to work for everyone. There’s no magic concurrency that’s going to be right for anyone, and changing the current behavior would be a breaking change for many.

Instead - I am going to recommend that y’all take a look at p-queue: https://github.com/sindresorhus/p-queue

We use this internally for a lot of our modules, and we’ve been really happy with it. Using this with googleapis should be pretty easy 😃

Let us know what you think!

[jmdobry]

getaddrinfo ENOTFOUND sounds like a connectivity, or that it’s intermittently failing to resolve the dns. I’ll have to give your code a try.