Comment Re:Can someone explain node's supposed speed (Score 1) 319
Just to add, that the event driven thing makes a difference where you're doing lots of small transactions - in that case, you can support thousands of incoming requests with just one process using a relatively small amount of RAM. You can really make it fly by locking it to a CPU core and giving it real-time priority. If you expand that out to all but one of your system's cores, then assuming you have the ram, one box can serve nearly everyone on the planet, just so long as no one asks for anything too complicated. That's a pretty specialised use-case, which very few of us really need to think about.
However, as you say, almost no one really needs to squeeze the last few percent of performance out of any web app they're running. Your boss might complain about the cost of another server, but it's easily manageable in the grand scheme of things. That being the case, having a slightly inefficient stack, and some occasional cross-core IPC, in exchange for keeping your systems pretty close to vanilla, and keeping your code, testing and deployments super-simple makes a lot of sense.