Why await Doesn't Block Node.js

A common misconception is that await makes Node.js sit idle until an operation completes.
Consider a database query that takes 200ms.
Many developers imagine the JavaScript thread spends those 200ms waiting for the response. That's not what happens.

When an async function reaches an await statement, execution of that function is paused. The underlying operation continues through the database client and operating system I/O mechanisms while the event loop remains available to process other work.

Once the query result arrives, Node.js schedules the continuation of the async function and resumes execution after the await.
This execution model allows a single Node.js process to manage thousands of mostly I/O bound requests without dedicating a thread to each connection.

Limitation

This benefit applies primarily to I/O bound workloads.
CPU intensive operations such as image processing, large JSON transformations, encryption, or complex calculations still execute on the JavaScript thread. When CPU work dominates request processing, event loop responsiveness decreases and concurrency suffers.

Understanding this distinction is critical when evaluating Node.js scalability.