"Go beyond framework APIs to understand the Node.js event loop, concurrency, streams, memory, networking, and graceful shutdown."

The more serious my backend engineering work becomes, the less satisfied I am with knowing only the framework APIs.

NestJS and Express are useful abstractions.

But eventually, understanding the runtime underneath them becomes important.

A framework can help organize an application, enforce architectural boundaries, and simplify common backend operations. It cannot eliminate the runtime behavior of the code we write.

When an application becomes slow, memory consumption increases, requests begin timing out, or background work interferes with API responsiveness, the explanation may have little to do with the framework itself.

It may be a consequence of Node.js executes JavaScript, manages asynchronous operations, handles data, or uses system resources.

That is why I consider runtime knowledge an important part of backend engineering.

The framework is not the runtime

When we…