Re:An update on JavaOne
by swannodette on Friday August 27, 2010 @08:23PM
(#1640778)
What you mean is that your real-time application was largely memory bound - other apps might require that sanely and rapidly coordinating access to shared state might be more critical than the cost of memory- with a collaborative whiteboard or the backend of a MMORPG you're probably going to run into difficulties with C/C++ and Node.js might very well be useless. There are domains where shared nothing just doesn't work.
A while ago I rewrote a system from Java (that used JBoss Netty) to node.js. The node.js solution used about 10x less memory. And memory is a crucial element of scaling real-time web applications.