There are a few ways you can run NodeJS on Windows for production workloads.
It's important to first understand that Windows has built-in (kernel mode!) support for HTTP servers called HTTP.sys which IIS and other web-servers use to serve HTTP traffic rather than simply opening a listening socket on port 80 (this is how Microsoft's IIS beat the pants off Apache in the web-server benchmarks back in the late 1990s).
Your options are:
Expose NodeJS directly to port 80/443
- This is the simplest approach though with many drawbacks. But provided you don't need to run different multiple applications and non-NodeJS code on the server then this is a valid option. Just remember to disable
HTTP.sys first.
Run NodeJS behind HTTP.sys
- The author of the
iisnode library also wrote another lib called httpsys for NodeJS (as running behind IIS uses many of the same techniques as running behind HTTP.sys): https://github.com/tjanczuk/httpsys - unfortunately it's out of date, but there really isn't much code to it so you can probably hack it yourself to work with the latest versions of Node. This is one of the points of open-source! ("Don't complain, fix it!")
Run NodeJS behind IIS with Microsoft's fork of iisnode:
- While the original
iisnode is abandoned, Microsoft actually took over ownership and forked it to https://github.com/Azure/iisnode which does seem to be actively maintained - and Microsoft has a vested interest in maintaining it because Microsoft wants to make money from the world running its apps on Azure regardless of whatever language, platform or OS they're using.
- ...though it seems MS isn't releasing binaries (not since 2017), so you'll have to build it yourself (for details, see my footnote).
Run NodeJS behind an nginx port for Windows
One last option (and probably the best for your situation) is to run NodeJS on Windows as-is and use IIS' Application Request Routing (ARR) feature:
Regarding Azure's fork of iisnode:
As it's 2024 now, and because the azure/iisnode fork hasn't made any releases since 2017, I felt I should do a quick-check to see how, exactly, Azure employs iisnode; for example, to see if they have a private build.
...and I found Azure is runnning a private build 2.27.0 of their fork of IISNode which was built in January 2018, while the last public release was 2.26 in Feb 2017.
...but if you want 2.27 to download for yourself, I've exfiltrated the binaries from Azure and posted them to a related Issue in their repo.
Interestingly, there have been a bunch of commits made since 2.27 was built, so most people are better-off making their own build of iisnode rather than using the exfiltrated binaries above.
node.jsapplication on windows server (for production) and on windows 10 (as service, without console window opened, if it is possible). – Advertent