Node.js, why is this useful?

Question

I am a .net web developer. I like to learn new languages ​​and try to be updated with their various functions.

I have heard about node.js for some time. I finally had a few days off, so I decided it was a good opportunity to learn.

With a quick look at the node documentation, I have to say that I did not understand what the whole problem was about. As an experienced .net programmer, why should I learn node.js? Does it replace my C # code? Can a node really compete with a point network (database support, multithreading, OOP, readability, etc.)? Are you really faster developing with node.js?

Answer 1

As an experienced .net programmer, why should I learn node.js?

For example, if you are interested in the asynchronous programming model or if you want to use the same language in your client / server stack or want to try to do something a little different and so on ...

Does it replace my C # code?

In general, it can replace and complement the various parts of your existing applications (and not only) written in C #, however, this may depend on the script and whether it is suitable for using templates and paradigms that are used with node.js.

Can a node really compete with a point network (database support, multithreading, OOP, readability, etc.)?

Node.js has a very active community that has so far developed around 4.5K packages that cover a wide range of areas, functionality and systems, for example, you should be able to find several packages for each main (and even small) database system without problems.

Are you really faster developing with node.js?

Node.js is less detailed in the amount of code than C #. The area in which it stands out is, for example, network programming. Its network-related API is pretty simple, and you should write such programs quickly. Of course, this is not limited only to network materials, for example, node is widely used in Internet-based applications (in real time). However, you should be careful with asynchronous / callbacks and study or read some articles about this material before plunging into lifeless in node.

Answer 2

For me, the basic concept of node.js is related to high latency operations without explicit multithreading. Non-processor IMO applications should not need multithreading. Multithreading adds a lot of complexity, but is not really needed when working with I / O latency.

But I am sure that this style of programming will become more popular in the .net world. C # 5 gets an async language function that greatly simplifies this programming style. Therefore, as soon as you get the appropriate libraries, you can write asynchronous multi-threaded code in C # very well.