> is Node and JavaScript feasible to create complex and long living applications If you know how to quench fires like this one: http://techblog.netflix.com/201

> is Node and JavaScript feasible to create complex and long living applications If you know how to quench fires like this one: http://techblog.netflix.com/2014/11/nodejs-in-flames.html http://techblog.netflix.com/2014/11/nodejs-in-flames.html > Not only SAP and other behemoths, but complex web applications like online banking and other similar business-critical system. I'm sure the tech can do it, and the asynchrony pays off in performance in some applications. Consider using Java instead. There's a reason why Java is still around in the enterprise, and that it's version (assuming it follows semver), is still at 1.x. > ES6 is adding classes that will make JavaScript more familiar to developers from other languages. It's just sugar. It's still prototypal inheritance underneath. If you start thinking that JS classes are like classical OOP classes just because JS now has classes, then you're in for a lot of hurt. > Is there some unique advantage that Node can offer over the more traditional languages like Java, ASP and PHP that are more mature Besides the fact that you can prototype apps in half the time and mashing the keyboard gives you Mona Lisa? Nothing really. If you look closely at the JS community, they're trying to solve problems that have already been solved in other languages (streams, module management, socket connections, p2p, better syntax etc.) > is it just better to leave JS for integrations and other simpler tasks Yes. As a JS dev since forever, JS is best suited for quickly prototyping apps (Phonegap comes into mind), mock servers and API endpoints (express is good on this one), bots and automation (chatbots are a good example). For other tasks like banking, security, gaming, business etc, look elsewhere.