> My company's customer-facing API bits are written in nodejs, First mistake. If the argument is about performance, then using nodejs is really a bad choice i

> My company's customer-facing API bits are written in nodejs, First mistake. If the argument is about performance, then using nodejs is really a bad choice in general. Node promises are already expensive on memory and can easily cause memory leaks if not handled properly. > and our VP insists that we are not allowed to use async/await, and must instead use Bluebird promises [1]. I don't think Bluebird will solve the problem and is more likely to break on new versions of node that have critical security fixes. If you are seriously after performance with strong concurrency characteristics, use Go instead.