forever

Promises and now async/await go a long way to remedy the discrepancy between synchronous exceptions and asynchronous errors, by helping ensure that they both end up as promise rejections (as long as promises/async functions are your de facto async abstraction) while also being handleable with try/catch. The Koa framework (and in the future Express I believe) is designed around this concept, so middleware-level promise rejections can be handled in a single place, and by default simply produce an HTTP error response. It is a shame that it's going to take a while for the Node stdlib to catch up, however. Also I thought something like PM2 (https://github.com/Unitech/pm2) or Forever (https://github.com/foreverjs/forever) was pretty much standard for production Node apps?

Wish they'd do a full write-up. I'd be interested in how they run their node processes. - Using containers, VMs, bare metal? - Using a process manager like Forever[1], PM2[2] or just native systemd? [1] https://github.com/foreverjs/forever [2] https://github.com/Unitech/pm2