Understanding I/O Models: From Blocking to Asynchronous and Their Role in Java NIO2 and Node.js

It is well known that recent Java versions have added support for Java NIO and NIO2, while one of the most praised advantages of the Node.js stack is its high‑performance I/O; this article discusses the underlying operating‑system technologies that enable both.

Why did Node.js and Java NIO2 not appear earlier? The author believes the supporting low‑level technologies were not mature enough.

The underlying technologies are OS‑level I/O mechanisms. Both Java NIO2 and Node.js are user‑space (application‑layer) technologies that rely on OS advances. Historically, C/C++ benefited first because OS system calls are most naturally used from those languages; other platforms later wrap these calls to provide more convenient APIs.

Regardless of OS design, five I/O models are indispensable:

Blocking I/O – simple to program but blocks the calling thread, wasting CPU cycles.

Non‑blocking I/O – avoids blocking but requires busy‑waiting (polling), still consuming CPU.

I/O multiplexing (select, poll, epoll) – the most stable model today, used by many mainstream applications including Node.js; platforms often add a layer on top to support asynchronous I/O.

Signal‑driven I/O (SIGIO) – rarely adopted due to limited performance benefits and unstable OS support.

Asynchronous I/O (POSIX aio_ functions) – the ideal AIO model with simple programming, but few OSes fully support it; Linux is making progress, and many frameworks simulate AIO in user space.

Images illustrating each model are included in the original article.

The article also clarifies the difference between synchronous vs. asynchronous (interaction between application and kernel) and blocking vs. non‑blocking (behavior of threads/processes).

In summary, the evolution of high‑performance runtimes like Node.js and Java NIO2 is tightly coupled with OS‑level I/O advancements, and understanding these fundamental models helps developers appreciate the motivations and trade‑offs behind modern I/O APIs.