1 views collected around this technical thread.
This article explains Netty's asynchronous architecture, compares BIO/NIO/AIO models, describes its thread and pipeline designs, evaluates real‑time communication options, and provides complete frontend and backend code examples for creating a WebSocket‑based instant messaging service using Netty and Spring Boot 3.
This article provides a comprehensive overview of Netty's core layers, protocol support, transport services, logical architecture, various I/O models, packet framing techniques, custom protocol design, write‑and‑flush behavior, off‑heap memory management, and high‑performance data structures such as FastThreadLocal and HashedTimerWheel.
The article analyzes the high load and low CPU utilization problems of a Java service, compares various I/O models, introduces coroutine fundamentals and the Quasar library, demonstrates practical migration steps with code examples, and evaluates the performance gains and risks of adopting coroutine‑based concurrency.
This article examines why Netty has become the preferred high‑performance server framework over Tomcat, covering Java I/O models, zero‑copy techniques, off‑heap memory usage, and Netty’s custom object‑pooling, and explains how these features enable handling thousands of concurrent connections efficiently.
This article explains Redis's high‑performance I/O architecture by tracing the evolution from blocking, non‑blocking, and multiplexed network models to various Reactor‑based thread designs, illustrating each model with Java pseudo‑code and diagrams to clarify why Redis adopts a single‑threaded Reactor with optional multi‑threaded I/O extensions.
This article explains the structure and principles of Tomcat connectors, describes how they handle network IO through components like Endpoint, Processor, and Adapter, and compares the synchronous NioEndpoint with the asynchronous Nio2Endpoint using various IO models and multithreading techniques.
This article explains the principles of event‑driven programming, compares traditional linear execution with event‑driven models, and details various I/O models—including blocking, non‑blocking, multiplexing, signal‑driven, and asynchronous—providing Python code examples and discussing their advantages and use cases.
This article explains the two main network I/O architectures—thread‑based designs such as one‑connection‑per‑thread, pre‑forked processes, and their pros and cons, as well as event‑driven designs like the Reactor pattern, thread pools, and multiple reactors—helping readers choose the appropriate model for different server workloads.