[dba-Tech] Node.js and IIS

Hi All:

Here is an interesting article on Node.js versus ASP.Net. It installs
Node.js within an IIS framework, not it natural environment (a web server
within a webserver) and then it compares the performance results. Microsoft
has created an application call IISNode for just such a task. This is a test
performed by a Microsoft developer.     

http://rarcher.azurewebsites.net/Post/PostContent/19

Microsoft is fully supporting Node.js or Node and will have/has libraries,
powershells, JavaScript script for Node, an adapter like IISNode. IISNode
automatically extends Node to all the CPUs (Node defaults to only one) on
the server and Node give IIS multiple socket capabilities (IIS currently has
only single socket capability... These implementations will all be OSS.

http://www.tikalk.com/iisnode

Being able to leverage Nodes multi-socket capability will give IIS a huge
advantage. If applications and data sources are not within your immediate
network, in order to retrieve information your IIS listening post would have
to manage each source sequentially. If one source was not responding in a
timely manner the entire process could choke.

Having multiple sockets will allow you to fill a page with data from a
accounting database, a client list or even manage fail-over situations, all
at the same time. Examples: if you are monitoring multiple feeds from stock
tickers, remotely managing a number of pieces of hardware, just acquiring
tweets from tweeter as well as a number of different (types of) databases.

Right now browsers using webkit HTML5, have multi-socket capabilities but
this performance feature will be rendered useless if your host backend is
vanilla IIS 7 or less. The good news is the next releases of IIS will be
able to handle multiple sockets.

I will be installing a new IIS web server along with Node on it but due to
prior commitments that process can not be attempted until later in March. As
soon as the new server is up and running I will post any issues and methods.

Jim