4 ms·
Java isn't really that good fit for real-time web applications as it usually eats a lot memory - especially if you compare it to C/C++ or node.js (V8). A whil
by amix 16y ago
Java isn't really that good fit for real-time web applications as it usually eats a lot memory - especially if you compare it to C/C++ or node.js (V8).
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.
- swannodette 16y agoWhat 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.