Thanks for the quick reply Kevin ! Is it true that NodeJS is not suitable for CPU intensive tasks and more suited for apps that do a lot of IO like database connections or calling third party web-services and just return JSON data ?
On Thursday, February 14, 2013 7:31:01 PM UTC+5:30, Kevin Swiber wrote: > > > On Feb 14, 2013, at 8:48 AM, kanitkar...@gmail.com <javascript:> wrote: > > > Hi, > > > > I would like to ask following questions to people who are expert & have > used NodeJS for Production ready application. > > > > 1) Why should I choose NodeJS for a large scale app which deals with > data related to Stock Market ? > > It certainly depends on what you're doing with that data. Can you > elaborate on the I/O and CPU requirements? If your app needs to spend lots > of time on computation, there are different strategies to gain performance. > In general, Node.js apps tend to have higher I/O requirements than CPU. > > > 2) Will the "Frequent Updates" way of fixing bugs and adding new > functionality stop in near future & be replaced instead with a stable > release ? > > I don't know how near it is, but that is the plan for the future, as I > understand it. Post-1.0, updates will likely come less frequently. Check > the API docs. Those APIs marked "Stable" will not change. > > > 3) How can I deploy my NodeJS project for Production use ? Do I have to > host .js files on server ? > > Node doesn't specify a preferred way of deployment. Deploy code however > you deploy code. To spin up a server, you can `node server.js` or use any > number of utilities for starting/stopping/restarting processes. > > > 4) What is good learning material for NodeJS ? > > http://nodejs.org/api/ - The API is the go-to when you need to understand > what the core library does. > http://howtonode.org/ - Blog posts regarding various ways to use Node.js. > http://www.nodebeginner.org/ - I haven't actually read this, but I've > seen it mentioned before as a good starting point. > > > 5) Are there any full proof benchmark tests done that can demonstrate > NodeJS's claims to be faster ? which can be shown to management of a > company for approval ? > > I'd recommend doing your own benchmarks based on your own particular > needs. Publicly-posted benchmarks can be very misleading and sometimes > magically reflect an outcome that benefits the person posting the results. > If you run into issues benchmarking Node, this list is a good place to ask > questions. > > Good luck! > > Regards, > > Kevin Swiber > @kevinswiber > https://github.com/kevinswiber -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- 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 nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
