LinkedIn Mobile Moved from Rails to Node: 27 Servers Cut and Up to 20x Faster
If you are thinking about using node.js for this reason[1] on most sites, you are optimizing poorly. LinkedIn didn't worry about this until after they were a public company.If Python/Djando or Ruby/Rails can get your app out the door and into customer hands faster, it is almost always the right thing to use.1. There are certainly other, very valid, technical reasons for choosing node.js over other technologies early. But let those reasons be about the problems you are solving today, not the ones you might need to worry about when you have 50 servers to deal with.