How I Built a Mini‑Netty from Scratch: Lessons in Java NIO Design

This article is the final piece of the "From Zero Hand‑write Mini Netty" series, aiming to show that network programming is not as hard as it seems by building a Mini‑Netty framework step by step.

1. Quick Navigation

Java NIO Basics – Why we keep forgetting Java I/O streams? (I/O Stream Guide)

From Stream to Channel – Mastering all file read/write scenarios with Java NIO

Series Part 1 – Fully understand Java NIO network model design principles

Series Part 2 – Designing a multi‑threaded Java NIO server model

Series Part 3 – Solving Java NIO packet‑sticking and half‑packet issues

Series Part 4 – Overcoming Java NIO buffer size limits

Series Part 5 – Designing a responsibility‑chain business dispatch model

Series Part 6 – Implementing heartbeat detection for long‑living connections

2. Article Journey

1. Single‑thread NIO program Initially I wrote a simple single‑thread network program using the raw Java NIO API that could handle TCP connection events.

2. From single‑thread to multi‑thread The single‑thread approach lacked processing capacity, so I introduced a multi‑thread model with an EventLoop.

3. Reading and packet‑sticking problems Multi‑thread handling revealed TCP message sticking, which I solved by adding a context buffer and custom message boundaries.

4. Writing message issues After fixing reads, writes could overflow the network buffer, so I added a write‑listener mechanism.

5. Decoder and business handler coupling The tight coupling between decoder and business handler led me to adopt the responsibility‑chain pattern, making processors pluggable.

6. Keeping long‑living connections active With pluggable processors, I added custom event listeners, idle detection, and heartbeat packets to ensure stable long‑term connections.

3. Significance of Mini‑Netty

Through iterative development, the tiny Java NIO program evolved into a Mini‑Netty framework featuring a thread model, protocol codec, pluggable processors, and heartbeat keep‑alive. Although not production‑grade, it reveals the design rationale behind industrial frameworks like Netty and T‑io.

4. Open‑source Code

All code for the series is open‑sourced on Gitee (https://gitee.com/linshidream/intrachat), with commit history matching each article for easy reference.

5. Future Plans

Next, I will start a new column "From Zero Hand‑write Netty Chat Application" to build a real‑time chat program similar to WeChat, covering end‑to‑end design from low‑level principles to full business flow.

Thank you for following along.