Short answer: Yes. Long answer: I am currently using it in production and it works great. It performs admirably, and is easy to use. I use to aggregate data r

Short answer: Yes. Long answer: I am currently using it in production and it works great. It performs admirably, and is easy to use. I use to aggregate data relevant to our business. It's basically a service I've written that anybody can send data to (in a particular format) to indicate that something happened. They can then subscribe to that "bucket" of data they have sent to the "collector" and it will let the subscriber know every time that event has happened. This is a classic example of what Node is excellent at doing. Extremely low-latency IO handling that involves little-to-no computation. It REALLY is that simple. Don't use Node for an application that is going to be a massive team effort (because sharing JavaScript code is a nightmare), and don't use it for an application that requires a good-deal of computation (something that you would use threads for in other languages/environments that isn't IO-handling). The problem is that using Node (and all other things) requires a value judgement. Exactly how massive is too massive? And exactly how much computation is too much? The computation question gets a bit tricky to, because if it's computation that is extremely complicated but won't be executed all that often then Node may still be the right tool for the job. The hype around Node is fading, because people "In the know", now have a clear understanding of what Node is good at and what it is bad at. The technical reasons why this is the case are not hard to grasp, but they take a while to explain and cannot be labelled as being "all-good" or "all-bad" (indeed Node's technical limitations have also given it some of its major strengths).