Nodejs.org is a static site. Nginx usually serves static sites faster than most dynamic servers, including node.js. Right tool for the job.
Most folks who run node.js in production either use some sort of external process monitor or the cluster module to cycle crashed processes. Some folks consider this approach simpler than managing threads. Others don't. A lot depends on the skills you have in house. -g On Monday, August 25, 2014 6:32:12 AM UTC-7, Manish Bansal wrote: > > Hi Friends, > I am very new to node.js and still exploring few opportunities where i can > use this server/technology for our development in a pilot project > effectively and efficiently. so far my experience is great, BUT the biggest > issue i found with node is (which is often advertised as pros) the > development technology + server is running in single thread. therefore any > unhandled unexpected exception which is causing due to > programming/environmental issues brings the server down. when i am thinking > about all other innocent users connected to my single threaded node > servers, my decisions gets influenced. > overthemore when i came to know Nodejs.org is also hosted on 3rd party > webserver "nginx" i took my step back of trying this attempts. > > Please share your thoughts. > > Manish Bansal > [email protected] <javascript:> > > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/fa376577-3ae5-4f7c-aa4d-42268827062f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
