Understanding the node.js event loop

The first basic thesis of node.js is that I/O is expensive:  So the largest waste with current programming technologies comes from waiting for I/O to complete. There are several ways in which one can deal with the performance impact (from Sam Rushing): synchronous: you handle one request at a time, each in turn. pros: simple cons: any one request can hold up all the other requests fork a new proc

[yssk22]

event loop