Hacker News new | ask | show | jobs
by tlrobinson 5649 days ago
The point is that putting a Node.js server behind a reverse proxy that uses threads (or processes) for concurrency is silly, since it quickly becomes the bottleneck, negating any benefits Node's asynchronous event-driven architecture provides.

If you want to do what you're suggesting you should use an equally performant web server like nginx, which is also asynchronous/event-driven.