Why Feat Is So Fast: The 2,000‑Line smart‑socket Core Explained

In a recent performance evaluation Feat demonstrated impressive numbers: roughly twice the throughput of Vert.x, latency as low as 0.89 ms, startup time under 100 ms, and memory usage far below Spring Boot. The author attributes these results not to exotic code in Feat itself but to its underlying communication layer, smart‑socket.

smart‑socket is the communication kernel beneath Feat, consisting of just over 2,000 lines of code.

The author explains that the small code base is an absolute metric of simplicity: with only 2,000 lines the core can be read in an afternoon, contains no hidden pitfalls, and avoids over‑design for speculative future needs. Fewer lines also mean fewer CPU cycles spent on irrelevant code, less memory allocation, and reduced garbage‑collection pressure, leading to higher performance and lower resource consumption.

smart‑socket implements the JDK AIO (NIO.2) interface spec but provides its own implementation. It redesigns the thread and memory models to eliminate three major issues of native JDK AIO—performance, memory, and stability pitfalls. The library exposes only two interfaces for extension: Protocol: defines how the framework decodes binary data. MessageProcessor: defines how received messages are processed.

There is no ChannelPipeline, no Handler chain, and no complex configuration. A minimal server can be started with a few lines of code:

// Server startup is that simple
AioQuickServer server = new AioQuickServer(port, protocol, processor);
server.start();

For developers familiar with network programming, the learning curve is essentially zero. smart‑socket follows the JDK AIO spec 100 % and fills the three native pitfalls with its own thread‑ and memory‑model design.

The library has evolved for over a decade, spawning related projects such as feat, smart‑servlet, and smart‑mqtt (the latter under 800 KB). The author emphasizes a personal principle: compare only with one’s past self, not with Netty or other frameworks, because each has different goals and requirements.

In the AI‑driven era, the need for simple, reliable, high‑performance communication grows with the proliferation of IoT, smart homes, industrial IoT, vehicular networks, real‑time push, game servers, and RPC frameworks. smart‑socket satisfies three key criteria: high performance (supports millions of concurrent long‑connections on a single machine), low entry barrier (only two interfaces to implement), and lightweight core (≈2,000 lines).

Project links:

Gitee: https://gitee.com/smartboot/smart-socket

GitHub: https://github.com/smartboot/smart-socket

Official site: https://smartboot.tech/