3 ms·
My understanding is that IIS is thread based. So wouldn't using it as a host/balancer inherently cripple Node? I mean I get the benefit of the possible inter-op
by virmundi 15y ago
My understanding is that IIS is thread based. So wouldn't using it as a host/balancer inherently cripple Node? I mean I get the benefit of the possible inter-op with .NET. However, I, and perhaps this is because I come from a Java background so I make things hard, would use Node.exe, but would have everything talk in more of an SOA manner. Node uses itself and other tools that are good for load balancing a tool like it and .NET talks to Node via services.
What am I missing?
- stevensanderson 15y agoIIS isn't blocking any of its threads once it's handed a request off to Node.js. IIS receives the incoming connection and proxies it via a named pipe into the Node.exe process, so the performance and capacity is much the same as if the requests went directly to Node.
- virmundi 15y agoThanks for the reply. It's interesting to so how MS is trying to involve themselves in public, interesting research.