Question

I have been looking into Node.JS and all the documentation and blogs talk about how it uses an event-loop rather than a per-request model.

I am having some confusion understanding the difference. I feel like I am 80% there understanding it but not fully getting it yet.

Answer 1

A threaded model will spawn a new thread for every request. This means that you get quite some overhead in terms of computation and memory. An event loop runs in a single thread, which means you don’t get the overhead.

The result of this is that you must change your programming model. Because all these different things are happening in the same thread, you cannot block. This means you cannot wait for something to happen because that would block the whole thread. Instead you define a callback that is called once the action is complete. This is usually referred to as non-blocking I/O.

Pseudo example for blocking I/O:

row = db_query('SELECT * FROM some_table');
print(row);

Pseudo example for non-blocking I/O:

db_query('SELECT * FROM some_table', function (row) {
  print(row);
});

This example uses lambdas (anonymous functions) like they are used in JavaScript all the time. JS makes heavy use of events, and that’s exactly what callbacks are about. Once the action is complete, an event is fired which triggers the callback. This is why it is often referred to as an evented model or also asynchronous model.

The implementation of this model uses a loop that processes and fires these events. That’s why it is called an event queue or event loop.

Prominent examples of event queue frameworks include:

• EventMachine (Ruby)
• Tornado (Python)
• node.js (V8 server-side JavaScript)