A contractor and I successfully convinced our large enterprise that node.js was the best choice for a new project and we were able to use it. I dont want to ma

A contractor and I successfully convinced our large enterprise that node.js was the best choice for a new project and we were able to use it. I dont want to make this a conversation about whether node is good or not, but it did hit the sweet spot as our goal was basically a RESTful API as a facade to some legacy tech, which is in my opinion where node shined - and this was back in early 2011. The convincing arguments are: 1) the technology fits the problem - I would not use C++ for a web api, and I would not use node for a rendering engine. 2) the team is (mostly) ready to use it - a couple weeks to read a book and make a prototype should be enough. There is no need for lengthy and expensive training sessions or a gigantic shift in technical knowledge 3) if it doesnt work out, you can double back quickly and cheaply 4) the new technology won't cost an arm and a leg - no need to find budget for expensive licensing for software/tooling 5) you are not proposing this alone - get backing from other senior level programmers/architects. If you can hit most of those, then you probably have a decent chance!