Understanding Java I/O: BIO, NIO, AIO, and Netty – A Comprehensive Guide

Java I/O Models

Java I/O is built on streams that can be classified as blocking (BIO), non‑blocking (NIO) and asynchronous (AIO). BIO creates a thread per connection and blocks while waiting for data; NIO uses a selector to multiplex many connections with fewer threads; AIO delegates the I/O operation to the operating system and notifies the application when it completes.

Key Differences

Blocking vs non‑blocking vs asynchronous behavior.

Byte streams handle raw binary data, character streams handle text.

Buffered streams improve performance by reducing disk access.

File I/O Examples

Typical code for reading a file with FileReader and writing with FileWriter is shown, as well as the buffered equivalents BufferedReader and BufferedWriter . Byte‑oriented I/O uses FileInputStream and FileOutputStream , optionally wrapped with BufferedInputStream and BufferedOutputStream .

Network I/O with Sockets

Simple socket programs illustrate the blocking nature of BIO, the need for multithreading, and the drawbacks of creating a thread per client. A thread‑pool version reduces thread‑creation overhead.

NIO Server Architecture

An NIO server uses ServerSocketChannel , configures it as non‑blocking, registers it with a Selector , and processes OP_ACCEPT and OP_READ events. Data is transferred through ByteBuffer objects.

Netty Framework

Netty is a high‑performance, event‑driven framework built on NIO. The article provides a minimal Netty server configuration that adds a StringDecoder , ObjectEncoder , and a custom handler extending ChannelInboundHandlerAdapter to process client messages.

Overall, the article serves as a practical guide for developers transitioning from basic stream I/O to scalable, non‑blocking network applications using NIO and Netty.