it's very likely that the hype is going to continue. The reality is that Node.js is the first system to be used by the enterprise. Enterprise skipped Ruby and PHP, and stayed with Java and .NET. Node is really well positioned to displace these technologies on the web tier of the enterprise.
I know this is advertising, but there are a couple of particularly objectionable points…
Increasing competition between rival internet companies, the speed of delivery and the ability to iterate are the key traits of market leaders. In a competitive scenario, reacting to end user needs, incorporating their feedback into the offering and delivering updates and changes regularly is essential.
This is literally nothing to do with Node. It's to do with good architecture and project management. The style of architecture generally used and encouraged in the Node community does tend to push SOA etc., but that's nothing to do with the language.
=========
Totally agreed,
Ability to iterate is nothing to do with node, however bringing node into an organisation with a 10 year old stack represents an opportunity to bring in new processes too. Out with old, in with new. Node is as about embracing a philosophy about how to build things.
=========
It’s extremely difficult to hire top talent these days; good developers like to learn new things and to use new technologies.
Node will not continue to be 'new technology' for long. This is a shoddy basis on which to select a tool.
=========
Disagree, ok in the long term there will be new things, but Node is only beginning, there's allot of runway here. 2-3 years at least before it's no-longer new and shiny.
========
double the number of requests per-second and reduced response time by 35% or 200 milliseconds.
Measuring reimplementations of code in alternative languages is frequently absolutely pointless, because that reimplementation will always go hand-in-hand with massive re-architecting, and absent second-system effect this will result in better performance. For example:
The old story of linkedin where moving to Node.js from Rails for their mobile traffic, reducing the number of servers from 30 to 3 (90% reduction) and the new system was up to 20x faster.
==============
These are real numbers, agreed it's easy to re-implement in a new language and scoff at an older system. Big question here is WHY DIDIN'T THESE COMPANIES JUST RE-IMPLEMENT IN JAVA?
==========
Because all of the rendering was pushed to the client, no doubt.
==========
Node is great, but it's one of many valid choices for developing huge, modern web apps. It's not that Node is becoming the "go-to technology in the Enterprise" (it's not), but that SOA, loose coupling and the reduction in use of monolithic frameworks are everywhere, and that's something that Node is good at.
============
I believe that history will show Node is becoming the go-to technology for the enterprise. It fits well with SOA, loose coupling etc .. + it's javascript (the most widely used language on the web).
Crazy, PayPal have thrown our java in favour of Node.js
This opens the door for the financial industry to get up to date and start innovating again. Big news for node.js