Node.js&nbsp;is best suited for real-time applications: online games, collaboration tools, chat rooms, or anything where what one user (or robot? or sensor?) does with the application needs to be seen by other users immediately, without a page refresh. I should also mention that Socket.IO in combination with Node.js will reduce your real-time latency even further than what is possible with long polling. Socket.IO will fall back to long polling as a worst case scenario, and instead use web sockets or even Flash if they are available.But I should also mention that just about any situation where the code might block due to threads can be better addressed with Node.js. Or any situation where you need the application to be event-driven.Also, Ryan Dahl said in a talk that I once attended that the Node.js benchmarks closely rival Nginx for regular old HTTP requests. So if we build with Node.js, we can serve our normal resources quite effectively, and when we need the event-driven stuff, it’s ready to handle it.Reasons to use NodeJS:<ul><li>It runs Javascript, so you can use the&nbsp;same language&nbsp;on server and client, and even share some code between them (e.g. for form validation, or to render views at either end.)</li><li>The event-driven system is&nbsp;fast, compared to traditional Java or ROR frameworks, when handling lots of requests at once.</li><li>The ever-growing pool of&nbsp;packages, most of which are conveniently hosted on github. Sometimes you can report an issue and find it fixed within hours! It’s nice to have everything under one roof, with standardized issue reporting and easy forking.</li><li>Seems rather suitable for agile development and&nbsp;rapid product iteration.</li></ul>&nbsp;Reasons&nbsp;not&nbsp;to use NodeJS:<ul><li>It runs Javascript, which has no compile-time type checking. For large, complex&nbsp;safety-criticalsystems, or projects including collaboration between different organizations, a language which encourages&nbsp;contractual interfaces&nbsp;and provides&nbsp;static type checking&nbsp;may save you some debugging time (and&nbsp;explosions) in the long run. (Although the JVM is stuck with&nbsp;<code>null</code>, so please use Haskell for your nuclear reactors.)</li><li>Added to that, many of the packages in NPM are a little&nbsp;raw, and still under rapid development. Some libraries for older frameworks have undergone a decade of testing and bugfixing, and are very&nbsp;stable&nbsp;by now.&nbsp;<a href="https://pinboard.in/u%3adandv/t%3anpm/t%3aagainst" target="" rel="" title="Link: https://pinboard.in/u%3adandv/t%3anpm/t%3aagainst">Npmjs.org has no mechanism to rate packages</a>, which has lead to a proliferation of packages doing more or less the same thing, out of which a large percentage are no longer maintained.</li><li>Nested callback hell. (Of course there are&nbsp;<a href="https://github.com/joyent/node/wiki/modules#wiki-async-flow" target="" rel="" title="Link: https://github.com/joyent/node/wiki/modules#wiki-async-flow">20 different solutions</a>&nbsp;to this…)</li><li>The ever-growing pool of packages can make one NodeJS project appear&nbsp;radically different&nbsp;from the next. There is a large diversity in implementations due to the huge number of options available (e.g. Express/Sails.js/Meteor/Derby). This can sometimes make it harder for a new developer to jump in on a Node project. Contrast that with a&nbsp;Rails&nbsp;developer joining an existing project: he should be able to get familiar with the app pretty quickly, because all Rails apps are encouraged to use a&nbsp;similar structure.</li><li>Dealing with files can be a bit of a pain. Things that are trivial in other languages, like reading a line from a text file, are weird enough to do with Node.js that there’s a StackOverflow question on that with 80+ upvotes. There’s no simple way to read one record at a time from a CSV file. Etc.</li></ul>Node.JS AlternativesThere are other option to use in place of Node.JS however&nbsp;<a href="http://vertx.io/" target="" rel="">Vert.x</a>seems to be pretty promising and has lots of additional features like polygot and better scalability considerations.

REASONS TO USE NODE.JS

Useful links

Company

Information

Content Writers

Freelancers

Freelance Jobs

Online Jobs

Designers

Developers

Translations