Faster Node.js Application

So our users have happily deployed node.js applications to production, for months! Despite some minor issues, node.js have been proven to be quite perform, and even reliable (thanks to cluster management). Given a break, I got some chances to look at more aspects of the application, framework and beyond to squeeze out more from node.…

node-thesus vs node-inspector

So i’ve been using brackets.io for a while, quite pleasant, and now there’s https://github.com/adobe-research/node-theseus added, it seems my favorite https://github.com/node-inspector/node-inspector debugging support for node.js has a little competition here. But i soon realized some problems or limitations of thesus: it needs node-thesus to run ur app, not node, expect some code change for ur app or testing…

npm-shrinkwrap could shrink better

Unlike most of our team’s developers, who already got the latest mac pro (quite high end), my poor old thing doesn’t have any SSD, and a bit shy with its limited RAM & CPU got me a bit unhappy. Coz we’re creating larger app using node, more & more modules are to be loaded each…

Making node.js operational — robustness

Apart from the new features added, I also carefully reviewed the performance aspects, and did some enhancements for the sake of robustness. One observation from the real production application was that, GC would become a problem, sooner or later, and when it comes, it comes badly. I tried using –nouse-idle-notification and mitigated the problem noticeably,…

Making Node.js operational

It occurs to me that much as the node.js community and the usage grow, lots of java or other developers still figure it as premature and reject it for enterprise applications. To some extent, I found their conservation reasonable, and the major reason for that could be the operational gap. A fundamentally different architecture requires…