Node.js Explained

Altamira TC · 180K views · 2012 · 29:16

Open on YouTube

Web developmentSoftware architecture & designtalkdated

Why Stack Overflow recommends it

Stack Overflow users link it when explaining why Node.js is single threaded, how its event loop differs from Apache-PHP or IIS threading, and why Node suits beginners.

Recommended by 3 people across 3 different months, 2013 to 2014.

What it is

A 29-minute 2012 conference-style talk by Jeff Kunkle that explains the theory and programming model behind Node.js, including its single-threaded event loop. It covers the benefits and challenges that approach brings.

What people said

Recommends whirlwin · 2013-07 · Stack Overflow · on “Why is Node.js single threaded?”

I recently watched a good video (29 mins) explaining some of the theory behind Node. I even think the guy talks about CPU intensive tasks and briefly how to handle them: [this video]

Recommends Karthic Rao · 2013-10 · Stack Overflow · on “beginner node.js: do I really need a full app?”

First , Its not a bad idea to use node.Js to satisfy your requirement,the uniqueness of NODE and added advantage compared to conventional technologies like Apache-PHP is clearly explained in this following video Why Node.JS is better [this video] .The notion of NODE being just used for advanced or complex applications is wrong , you can use node for building applications which are very simple to anything of huge proportion.It would be a not so comfortable task for a node beginner to code without using any frameworks , but by using this web application framework called express [LINK] , you need not code from scratch and its very easy to setup html pages using its simplified html templating languag

Recommends barry-johnson · 2014-02 · Stack Overflow · on “Requests mechanism of Node.JS and IIS (event-loop and threading)”

I think the author you link to adds more confusion than clarity (the guy says he is just learning node, so you're really asking for a blind-leading-the-blind situation in using it to learn from). I don't know why he thinks that Node claims "it" (i.e. Node.js) is single threaded. I have never seen that. The point is that within Node your code all executes in a single thread which means you the developer are freed from dealing with contention of different sorts. (Many people see this as a key advantage, but I think one could argue that you are simply trading one kind of boilerplate (for semaphores or the like) for another: the handling of asynchrony (although several approaches exist for reduc