How node.js really works...

Bruno Trindade Bragança — Fri, 25 Sep 2026 10:21:06 +0000

I'll start here with a mantra:

Stop waiting on I/O. Let the event loop do the work.

So, why am I telling you this? Do you know how node.js handles each request, and how it may help you to have a better experience in your software?

Imagine a restaurant with a single waiter.

In traditional server architectures (synchronous by default, like Java or C#), when a customer orders food, the waiter takes the ticket to the kitchen and stands idle at the counter waiting for the chef to finish cooking. No other customer gets served until that single meal is ready. To handle 100 customers, you need 100 waiters—which gets expensive and chaotic to manage.

Node.js changes this model completely!

It operates on a single thread with a smart event loop. The waiter takes your order, sends it to the kitchen, hands you a call buzzer, and immediately moves to serve the next customer in line. The waiter never wastes time standing still.

When your food is cooked, the buzzer rings (an asynchronous callback), and the waiter picks up the dish to hand it to you between taking new orders.

Key takeaways for Node.js concurrency:

Non-blocking I/O: Reading database records, files, or network calls happens in the background.
Single Thread Efficiency: One process handles thousands of concurrent connections without CPU idle time.
Lower Complexity: Eliminates thread synchronization bugs and heavy memory overhead.

Now, the real explanation direct from Node.js documentation:

A Node.js app runs in a single process, without creating a new thread for every request. Node.js provides a set of asynchronous I/O primitives in its standard library that prevent JavaScript code from blocking. In addition, libraries in Node.js are generally written using non-blocking paradigms. Accordingly, blocking behavior is the exception rather than the norm in Node.js.

When Node.js performs an I/O operation, like reading from the network, accessing a database or the filesystem, instead of blocking the thread and wasting CPU cycles waiting, Node.js will resume the operations when the response comes back.

This allows Node.js to handle thousands of concurrent connections with a single server without introducing the burden of managing thread concurrency, which could be a significant source of bugs.

Source: introduction-to-nodejs

Again, stop waiting on I/O. Let the event loop do the work.

DEV Community: Bruno Trindade Bragança

How node.js really works...