About Node.js in Action

[Runrioter Wung]

Node is very, very hot, and I just coded in javascript for the front-end before.I wonder when I should choose JS for backend not .NET or JavaEE(I am a J2ee programmer). Which type of application is the one that Node is designed for?Asyncronous and evented nature of Node is very cool,but sometimes sequential programming is a must.How can I implement it by JS.I don't know that if all I ask is in the book named NODE.JS IN ACTION.

[Mike Cantelon]

Runrioter Wung wrote:Node is very, very hot, and I just coded in javascript for the front-end before.I wonder when I should choose JS for backend not .NET or JavaEE(I am a J2ee programmer). Which type of application is the one that Node is designed for?Asyncronous and evented nature of Node is very cool,but sometimes sequential programming is a must.How can I implement it by JS.I don't know that if all I ask is in the book named NODE.JS IN ACTION.

Hi Runrioter,

Node.js is great for applications that require high concurrency and minimal CPU/memory usage. So things that should feel "real-time" like online games, chat, and web applications. For a balanced look at what use-cases Node.js is most suitable for, I recommend Chris Richardson's talk "Node.JS: The Good Parts? A Skeptic's View" (https://www.youtube.com/watch?v=CN0jTnSROsk).

If you need part of your application to be sequential, you can a technique called "flow control". Flow control makes asynchronous logic behave in a synchronous fashion. You can either implement flow control yourself in your application or, much easier, simply use flow control modules. One such flow control module is async (https://github.com/caolan/async).

Cheers,
Mike

[Runrioter Wung]

Mike Cantelon wrote:

Runrioter Wung wrote:Node is very, very hot, and I just coded in javascript for the front-end before.I wonder when I should choose JS for backend not .NET or JavaEE(I am a J2ee programmer). Which type of application is the one that Node is designed for?Asyncronous and evented nature of Node is very cool,but sometimes sequential programming is a must.How can I implement it by JS.I don't know that if all I ask is in the book named NODE.JS IN ACTION.

Hi Runrioter,

Node.js is great for applications that require high concurrency and minimal CPU/memory usage. So things that should feel "real-time" like online games, chat, and web applications. For a balanced look at what use-cases Node.js is most suitable for, I recommend Chris Richardson's talk "Node.JS: The Good Parts? A Skeptic's View" (https://www.youtube.com/watch?v=CN0jTnSROsk).

If you need part of your application to be sequential, you can a technique called "flow control". Flow control makes asynchronous logic behave in a synchronous fashion. You can either implement flow control yourself in your application or, much easier, simply use flow control modules. One such flow control module is async (https://github.com/caolan/async).

Cheers,
Mike

Nice! Thank you for your reply!
Cheers!

[Bhushan Jawle]

Hi Mike
Is the book focus intended for developer with web background new to node.js or some node.js knowledge is required.
Like I read somewhere when it comes to node.js, some people just "get it" the first time, others are trying to map it to something which they already know.
The reason to ask that question is I belong to second category as of now.
Regards
Bhushan

[David Sachdev]

I am anxious to watch this video as it seems like it will address some of my underlying questions about Node.js. Does the book get into comparing Node.js with other application servers and when Node is the right (and wrong) choice? Also, application servers turned into these monolith beasts that did everything...and then Rod Johnson, and his bunch came around and really changed that model quite a bit with Spring. Is there another application "server" that you would compare Node.js to, and do you think it is going to avoid the monolith beast syndrome that have ruined other app servers?

Thanks
David Sachdev

Runrioter Wung wrote:

Mike Cantelon wrote:

Runrioter Wung wrote:Node is very, very hot, and I just coded in javascript for the front-end before.I wonder when I should choose JS for backend not .NET or JavaEE(I am a J2ee programmer). Which type of application is the one that Node is designed for?Asyncronous and evented nature of Node is very cool,but sometimes sequential programming is a must.How can I implement it by JS.I don't know that if all I ask is in the book named NODE.JS IN ACTION.

Hi Runrioter,

Node.js is great for applications that require high concurrency and minimal CPU/memory usage. So things that should feel "real-time" like online games, chat, and web applications. For a balanced look at what use-cases Node.js is most suitable for, I recommend Chris Richardson's talk "Node.JS: The Good Parts? A Skeptic's View" (https://www.youtube.com/watch?v=CN0jTnSROsk).

Cheers,
Mike

Nice! Thank you for your reply!
Cheers!