Understanding Node.js: Single‑Threaded Event‑Driven Architecture and Event Loop

Node.js is a server‑side JavaScript platform known for its single‑threaded, non‑blocking nature, which is achieved through a callback mechanism and an event‑loop.

Key points highlighted include:

Single‑threaded execution: JavaScript runs on a main thread; heavy I/O is off‑loaded.

Event‑driven model: Modules listen for events and react accordingly.

Event polling (event loop): Producers enqueue events, consumers dequeue and process them, using a thread pool for blocking operations.

The architecture consists of three layers: the Node.js standard library (e.g., http, fs), Node bindings that bridge JavaScript to C/C++ APIs, and the runtime support layer (V8 JavaScript engine and libuv providing cross‑platform async I/O and a thread‑pool).

Event‑driven programming in Node.js is implemented by the EventEmitter module; many core modules inherit from it. Example server code shows how to create an HTTP server, listen for the “request” event, and respond:

var http = require('http');

var server = http.createServer();

server.on('request', function(req, res) {

res.end('event!');

});

server.listen(8888);

The article also walks through the event‑loop process with a step‑by‑step example using fs.readFile, setTimeout, and console logs, illustrating how synchronous and asynchronous operations are scheduled and executed:

var fs = require('fs');

console.log('start');

fs.readFile('readme.md', 'utf-8', function(err, data) {

console.log(data);

});

setTimeout(function(){ console.log('timeout'); }, 0);

console.log('ended');

Additional snippets demonstrate the order of execution for multiple setTimeout calls with different delays, reinforcing the principle that callbacks are processed in the order they are placed in the event queue:

setTimeout(function(){ console.log('sync-1'); }, 1);

setTimeout(function(){ console.log('sync-2'); }, 5);

setTimeout(function(){ console.log('sync-3'); }, 5);

In summary, Node.js achieves high concurrency by combining a single JavaScript thread with libuv’s thread pool, asynchronous I/O, and an event‑loop that continuously polls the event queue.