ASP.NET Core VS Nodejs

Posted by Nvn9999 under ASP.NET Core on 12/24/2017 | Points: 10 | Views : 16538 | Status : [Member] | Replies : 3
Hello Everyone,

I would like to know if some one has known/seen performance improvement of a application using core compared to Nodejs in real time.

And which one is faster?.

I need this information to out source one small project, and performacne should be top notch for us and is only the concern as well. So, I need your suggestion to go with core or nodejs.

And a C# developer manage all the capabilities of core?.

Your response is really appreciated.



Posted by: Sheonarayan on: 12/25/2017 [Administrator] HonoraryPlatinum | Points: 25

Go with .NET Core as assuming your background is .NET with C#. So you do not have learning curve for NodeJS.
There are many comparison where ASP.NET Core is compared with NodeJS and few have also proved that ASP.NET is many times faster than NodeJS.


Sheo Narayan

Nvn9999, if this helps please login to Mark As Answer. | Alert Moderator

Posted by: Giselle on: 12/27/2017 [Member] Starter | Points: 25

ASP.NET Core templates even make use of Bootstrap layouts and npm for pulling in client-side libraries. The versatility is a big deal because your investment in learning the language .

Nvn9999, if this helps please login to Mark As Answer. | Alert Moderator

Posted by: Sagarchavada on: 3/15/2019 [Member] Starter | Points: 25

Node.js :
Node.js is famously known for its single-threaded callback handler. It means that instead of handling every new HTTP request inside a dedicated thread or process it does it inside a single thread.
That makes the request handling in Nodejs single-threaded, whereas in Apache/PHP it is multi-threaded for instance. But Node.js takes advantages of that because it uses asynchronous system IO calls that does not block the request thread. When an IO call is made by the request thread, the IO call is executed on its own thread, and the request thread keeps going. When the IO call is done, a callback is fired on the request thread to handle the response.
This makes Node.js well-suited for IO bound applications, but also introduces the so-called “callback hell”, which can introduces cyclomatic complexity to your code.
The single-thread request handling can be clustered using Node.js native clustering, Nginx load-balancing with multiple application process, or Node.js process managers such as PM2, which makes use of all the server cores to start up as many application process as the CPU can handle.
ASP.Net :
The async/await pattern introduces asynchronous programing for request handling. Indeed, each request handlers can be tagged as asynchronous, and IO calls can be awaited, which means every request will run on its own thread, and each IO call inside the request handling will be non-blocking.
This Task-based model can make use of callbacks, promise, or async/await programing models.
ASP.Net Core advocates the use of the async/await pattern when writing IO bound web applications.

Nvn9999, if this helps please login to Mark As Answer. | Alert Moderator

Login to post response