There's another big advantage, nodejs doesn't need to be on a Microsoft Windows server - it can be no problem. Where as .NET requires Ms Windows Server. Ms licenses are expensive, the typical .NET stack also includes SQL Server which is another cost - and recent changes has meant that it's now priced per Core rather than per Processor. This all adds up and makes scaling more of a financial burden.
And nodejs is damn nice to work with. No reliance on Ms is great, sell your enterprise software to companies with Ms Servers and ones with Linux, Solaris etc... - mrdnk On 4 Jul 2012, at 18:32, Brad Carleton <[email protected]> wrote: > From a business perspective nodejs is cheaper. If you are building Internet > services, you know that you will be paying for infrastructure, servers, > storage, etc. You add another bundle of costs for software and licenses with > .NET. That puts you at a big disadvantage. The number of major Internet > players actually running Microsoft software consists of one company, > Microsoft. > > Here's an Oracle example, but ask Salesforce how much pain they are in right > now for running their backend databases on Oracle. > > Probably not the answer you were looking for, but as companies stop running > things in house and start moving more towards large Internet services, .NET > in its current form will become less competitive. > > Nodejs is built on a few very solid technologies/projects, and it is free all > the way down the stack. > > > On Tuesday, July 3, 2012 12:56:17 PM UTC-5, Justin Collum wrote: > 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 -- 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
