Had a discussion with a friend about Nodejs the other day. We are both C# / MVC / ASP.NET devs, with about 10 years experience. He asked me why someone would choose Nodejs over IIS + MVC . My argument was 1) performance 2) non-blocking IO. Keep in mind that I don't know a lot about node, I've built one small site and that's it. So my argument in favor was pretty short.
His response: Well, if I need performance on IIS I can just bump up the number of threads in the thread pool. Fair point. After looking into it a bit, it seems that the big difference between IIS + MVC and Node is that each thread can do more in the Node world because of the non-blocking IO. This cuts down on context switching and makes for better overall performance. Add that to the "one language to rule them all: coffeescript" factor and it's a clear win to me. Is that a fair summary of the performance advantages of Nodejs over IIS + MVC? Is there more to it? I'm aware that you can run Nodejs via IIS but my intuition tells me that won't be a good fit. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
