What is Node.js & How Does It Work?

The Event Loop: Node's Core Idea

Most traditional server languages handle each incoming request with its own thread, which works but doesn't scale well once you have thousands of simultaneous connections — each thread consumes memory whether it's doing real work or just waiting.

Node.js instead runs on a single thread with an event loop. When a request needs something slow — reading a file, querying a database, calling another API — Node hands that operation off and immediately moves to the next task instead of waiting. When the slow operation finishes, a callback fires and Node picks the result back up. This is what "non-blocking I/O" means in practice.

Why This Matters for Real Applications

This model makes Node.js extremely efficient for I/O-heavy workloads: REST APIs, real-time chat apps, streaming services, and anything that spends most of its time waiting on a database or network call rather than doing heavy computation.

It's less ideal for CPU-heavy tasks like video encoding or complex mathematical processing, since those would block the single thread. For those cases, Node offers worker threads, or you'd offload the work to a separate service.

npm: The Ecosystem That Made Node Unavoidable

Node ships with npm (Node Package Manager), giving you access to over two million open-source packages with a single `npm install` command. Need to parse dates, hash passwords, or validate emails? There's almost certainly a well-maintained package for it already.

This ecosystem is a major reason Node.js became the default for startups and enterprises alike — teams can assemble a production backend from tested building blocks instead of writing everything from scratch.

A Minimal Example

const http = require('http');

const server = http.createServer((req, res) => { res.writeHead(200, { 'Content-Type': 'text/plain' }); res.end('Hello from Node.js'); });

server.listen(3000);

This alone is a fully working web server — no external framework required. In practice, almost every real project builds on top of Express.js (covered in the next article in this series) rather than the raw `http` module, for cleaner routing and middleware support.