I am trying to convince myself to pick it up and start developing with it, but I want to know if anyone has expected stability issues or anything of the sort.

I understand it isn't "production" quality, like Apache or IIS. I figure for a small site, it should be fine (max of 200 concurrent connections). Should I assume this?

  • 2
    I think this should constantly be updated with new answers. Especially up to date answers on the biggest large scale use of Node.JS. – Bryan Field Mar 7 '11 at 23:33
  • I agree. I really would love to see how many people are truly using it. – Jeremy Boyd Mar 8 '11 at 15:51

Plurk.com uses Node.js for their Comet engine, they have a fairly high traffic load too.

Blog post about Plurk using Node.js


Since node.js has not been around long enough to have satisfied the greater community that it's stable and secure, many production deployments use Apache or nginx as a web server that proxies http requests to node running on a different port that is not accessible from the machine's public IP address.

Also forever may be able to help with the node stability issue.


Not a direct answer to your question but very related in terms of hosting node.js apps: two Heroku-like providers using node.js/JavaScript instead of Ruby, both in the beta/invite stage (as of mid-March 2011):


Looks like they pulled off some success stories from big companies. A good sign.

NodeJS.org now promotes articles from major companies Microsoft, eBay, LinkedIn and Yahoo.

I wonder what Google will do... They may already have evented I/O worked out behind the scenes. Or maybe they are just biding their time before they put their good name behind a product.

  • 1
    Google has produced Go which, while not event-driven, provides concurrency easily. – James O'Gorman Dec 19 '11 at 18:03

I use it as a reverse proxy in front of my sites - none are obscenely busy sites, but my image portfolio gets a lot of traffic.

I've not seen any random strangeness, crashes, or reliability issues to date.

  • 1
    Note that security is the big unknown. It started out with buffer overflow vulnerabilities. Whether it is all resolved is not yet known, but anyone implementing should keep their Node.JS up to date, in case there are some security items that got missed. (I'm no security expert) – Bryan Field Dec 19 '11 at 19:15
  • Is it faster then nginx or another proxyes you tried? – adrian7 May 13 '12 at 8:31
  • I'm not sure if it is faster - but I know it isn't slow - but it is definitely 100% more flexible. – user9565 May 14 '12 at 15:37

Not the answer you're looking for? Browse other questions tagged or ask your own question.