Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
After reading a lot of stuff about nodejs, I still ask my self :
What are the benefits over asp.net HttpAsync requests ?
The only limitation ( as I see) is the concurrent number of requests which IIS limits.
I tried to paint how I currently understand it :
any help ?
.net/ado.net can’t do that nodejs can ?
IIS limits the number of concurrent requests to a high number by default. The limit can be raised arbitrarily though.
There are two main benefits attributed to node.js:
ASP.NET does not support number 2 so that is an advantage.
Async IO and non-blocking code is fully supported by ASP.NET. Plus, you get the performance advantage of a JITed statically typed language. For that reason ASP.NET generally has superior performance to node.js for non-toy applications (printing “hello world” is not a real benchmark workload! neither is sleeping for 10 seconds).
node.js benefits from the extremely slim code-path it has. For that reason very minimal applications like “echo” or “hello world” are probably faster. This does not hold for apps which actually perform work.
So if you want to know which is “better” you need to consider a particular scenario. Benchmark with a realistic workload (no, calculating a factorial number is not realistic. C# is just going to win by a large amount. Means nothing). Also factor in maturity of the platform, libraries, documentation, support, developer productivity, ….