6

My understanding is that node.js is a python app that is geared towards the Linux world. Everyone seems to be quite happy with it's speed and ability to handle many concurrent connections.

I'm coming from a Microsoft background and think node.js might be able to be implemented using WCF.

Can someone tell me how node.js operates from a network background, and optionally provide insight if this can be ported to WCF or the Azure Service Bus?

makerofthings7
  • 60,103
  • 53
  • 215
  • 448
  • @Toby - Is the server part of 'node' not a Python application? See the response [here](http://social.msdn.microsoft.com/Forums/en-US/windowsazuredevelopment/thread/317e5cd4-dc89-4d01-a19d-1f9a38332c3c/) from Yi-Lun Lou – makerofthings7 Mar 14 '11 at 14:06
  • node is an evented i/o layer for the V8 JavaScript engine, written in C++ – Toby Hede Mar 15 '11 at 00:05

2 Answers2

3

Node is a Javascript framework that favors requires an event-driven approach to writing network services. Instead of blocking on networking operations, which is how network programming is usually done, Node gives you event handlers that are triggered when interesting stuff happens (clients connect, bytes arrive, DNS queries return, &c.).

As a consequence, Node is well-suited to and is being widely explored for realtime web apps. A host of interesting libraries for Node are now available, thanks to it being a Javascript framework. Some of them hide incredible power behind a very cute API.

There are binary versions of Node for Windows, but they are not deemed stable yet. Node is much lower level than WCF/Azure -- it's an event driven wrapper for sockets, DNS, HTTP, &c. if you will. It does not enforce any requirements as to how a networked service should be implemented (such as contracts or data marshalling) other than being event driven. I believe implementing a Node clone on top of those technologies would harm low-latency (at least), but perhaps someone more qualified can tell if it can be done.

PS. The Node website does a good job of explaining how it all works.

PPS. Possibly related, although I didn't have the time to read a lot about it, is Rx for .NET.

andref
  • 4,460
  • 32
  • 45
  • Since Node works at a layer lower than HTTP, then I would expect a whole ton of issues when a Proxy is involved... those devices are pretty picky on how the TCP session is built and what information is included in the HTTP headers. Does this sound right to you? ...would you expect issues with node.js and a proxy? – makerofthings7 Mar 14 '11 at 01:21
  • I would not - Node has built in support for HTTP too, it's not just plain TCP/UDP. The Connect and Express libraries can provide additional features (sessions, serving static files, basic auth) that the bare-bones http module does not. See [this question](http://stackoverflow.com/questions/5284340/what-is-node-js-connect-express-and-middleware). – andref Mar 14 '11 at 01:37
1

Node.js is a (really nice) programming model that's leveraging the great suitability of Javascript for asynchronous programming for implementing asynchronous web apps. The principle is very similar to the asynchronous programming model on Windows and especially in .NET (WCF supports this quite well) where all work is done on callbacks invoked by I/O threads and the app never locks a thread. Node.js creates a stringent JS programming model around this foundational mechanism to allow better scaling apps. So contrary to what a few folks here are saying, Node.js is quite exactly at the same layer/level as WCF. From a protocol perspective a Node.js implementation will likely always sit between the app and the HTTP listener provided by the underlying HTTP infra.

Clemens Vasters
  • 2,666
  • 16
  • 28