How does Node.js work in terms of network / TCP / HTTP? Can WCF mimic this?

Question

I understand that node.js is a python application focused on the Linux world. Everyone seems to be happy with the speed and ability to handle many concurrent connections.

I come from Microsoft's background and think node.js can be implemented using WCF.

Can someone tell me how node.js works with a network background and optionally gives an idea if it can be ported to WCF or Azure service bus?

Answer 1

Node is a Javascript framework for which supports an event-based approach is required to write network services. Instead of blocking network operations, as network programming usually does, Node provides you with event handlers that fire when interesting stuff happens (clients connect, bytes arrive, DNS queries are returned, etc.).

As a result, Node is well suited and widely studied for real-time web applications . A host of interesting libraries for Node is now available, thanks to its JavaScript structure. Some of them hide incredible power behind a very pretty API .

There are binary versions of Node for Windows , but they are not yet considered stable. Node is well below WCF / Azure, an event-driven wrapper for sockets, DNS, HTTP, and c. if you will be. It does not provide any requirements as to how a network service should be implemented (for example, contracts or data sorting), except that it is event driven. I believe that implementing a Node clone on top of these technologies can be detrimental to low latency (at least), but maybe someone more qualified can tell if this can be done.

PS. The Node website is a good help in explaining how this all works.

SFC. Perhaps related, although I did not have time to read much about it, Rx for .NET .

Answer 2

Node.js is a (really good) programming model that takes advantage of Javascript's great suitability for asynchronous programming for implementing asynchronous web applications. The principle is very similar to the asynchronous programming model on Windows and especially on .NET (WCF supports this pretty well), where everything works on callbacks called by I / O streams, and the application never blocks the stream. Node.js is building a rigorous JS programming model around this fundamental mechanism to better scale applications. Therefore, contrary to what some people say, Node.js is definitely at the same level / level as the WCF. From the point of view of the protocol, the implementation of Node.js will probably always be between the application and the HTTP listener provided by the basic HTTP interface.