NOTE
Using Netty
Building event-driven network clients and servers with Bootstrap, EventLoopGroup, Channel, Pipeline, handlers, and graceful shutdown.
This is a historical learning note and may contain outdated or incomplete understanding.
A typical Netty server creates event-loop groups, configures ServerBootstrap, chooses a channel implementation, installs channel options and a ChannelInitializer, binds a local address, and closes resources gracefully on shutdown.
The pipeline contains codecs and application handlers. Keep blocking database/filesystem/remote work off an event-loop thread unless it is deliberately offloaded, because one blocked event loop can delay many channels assigned to it.
Treat futures as asynchronous completion signals and define framing, timeouts, backpressure, connection limits, and ByteBuf ownership explicitly.