DEV Community: Alireza Naseri

Node.js Core: Event Loop & Native Power

Alireza Naseri — Fri, 27 Feb 2026 08:41:12 +0000

Title: Beyond the Hype: How Node.js Actually Handles Concurrency (Event Loop + libuv)

Post (Markdown):

Node.js is often described as “single‑threaded”, but that’s only true for JavaScript execution. The real concurrency story is asynchronous I/O + native code.

1) The Event Loop is an orchestrator
When you start an I/O task (filesystem, networking, DNS), Node.js delegates the heavy lifting to the operating system and/or libuv. Meanwhile, the JS thread stays free to keep the app responsive.

2) Why native (C/C++) matters
JavaScript can’t directly access low‑level OS primitives. Node relies on native bindings to bridge:

JS → C/C++ (libuv, V8 internals) → OS → back to JS

3) The thread pool is for “can’t block the loop” work
Some tasks are too expensive to run on the JS thread (CPU‑heavy or certain blocking operations). Node offloads these into libuv’s thread pool (configurable via UV_THREADPOOL_SIZE) to avoid freezing the event loop.

Key takeaway:

Single JS thread ≠ low performance. It means one thread for JS, plus native concurrency under the hood.

Hashtags: #nodejs #backend #javascript #performance #systems

Image (Concept Card):

How Moving to MVC Changed the Way I Write Express Apps

Alireza Naseri — Wed, 25 Feb 2026 10:01:49 +0000

When I first started learning Node.js, everything lived inside a single file.

Routes, business logic, and responses were tightly coupled — and it worked… until it didn’t.

At some point, my Express apps became hard to read, harder to test, and almost impossible to scale.

That’s when I truly understood why structure matters more than speed at the beginning.

Node.js is single‑threaded, but its event‑driven, non‑blocking nature is what makes it powerful.

Express makes HTTP handling simple — but MVC is what makes applications maintainable.

Why MVC actually helped me
MVC isn’t about adding layers for the sake of complexity.

Controllers handle request/response logic
Models represent data (not just databases)
Views render the output
A model can be a database, a file, or even an external API.

Once I separated these concerns, my code became:

Easier to reason about
Easier to test
Easier to extend without fear
A simple controller example

exports.getProducts = (req, res) => {
Product.fetchAll(products => {
res.render('shop', { products });
});
};
Clean architecture isn’t about writing more code.

It’s about writing code that survives growth.