This comprehensive guide explains the fundamentals of IO models—including blocking, non‑blocking, multiplexing, and asynchronous approaches—detailing their kernel interactions, practical Python examples, performance trade‑offs, and real‑world optimization strategies for high‑concurrency server applications.
This article explains the fundamental concepts of I/O models—including blocking, non‑blocking, multiplexing and asynchronous approaches—detailing their mechanisms, advantages, drawbacks, code examples in Python, and practical optimization strategies for high‑concurrency backend systems.
This article explains the fundamentals of input/output (IO) in operating systems, covering the basic IO concept, the role of the OS, the two‑phase IO call process, and detailed descriptions of blocking, non‑blocking, multiplexed (select, poll, epoll), signal‑driven and asynchronous IO models with example code.
This article explains the concept of IO, the role of the operating system, the complete IO workflow, and compares five common IO models—blocking, non‑blocking, select/poll/epoll multiplexing, signal‑driven, and asynchronous—highlighting their mechanisms, advantages, and typical use cases.
Aeraki Mesh 1.3.0 (code‑named Dragonboat) adds Istio 1.16.x compatibility, introduces connection multiplexing, enables MetaProtocol routing on gateways, expands Dubbo service governance options, provides Redis traffic management, and migrates official images to GitHub Packages, with a detailed changelog and configuration examples.
This article explains core Linux I/O concepts—including synchronous vs. asynchronous operations, blocking vs. non‑blocking behavior, user and kernel space separation, process switching, file descriptors, cache I/O, and the differences among select, poll, and epoll—providing a comprehensive overview for developers.
This article explains the four main I/O models—blocking, non‑blocking, multiplexed (event‑driven) and asynchronous—detailing their mechanisms, kernel interactions, performance implications, and how they differ in handling data readiness for network programming.
This article explains the four main I/O models—synchronous blocking, synchronous non‑blocking, I/O multiplexing (Reactor), and asynchronous I/O (Proactor)—illustrates their characteristics with examples, and encourages readers to share the content after gaining a clearer understanding of these fundamental backend concepts.
This article explains the shortcomings of HTTP/1.x, introduces the key innovations of HTTP/2 such as binary framing, multiplexing, server push, header compression, request priority, stream reset and flow control, and shows why mastering these concepts is essential for modern web development and interview preparation.
This article explains the concepts of blocking (BIO), non‑blocking (NIO) and asynchronous (AIO) I/O in Java, introduces the principle of I/O multiplexing, provides a complete Java example with server and client code, and compares system calls like select, poll, and epoll.
This article explains the five Linux I/O models—blocking, non‑blocking, I/O multiplexing, signal‑driven, and asynchronous—detailing their system calls, synchronization characteristics, and how they map to Java BIO, NIO, and AIO implementations, with illustrative analogies and usage scenarios.
This article introduces the five Linux I/O models—blocking, non‑blocking, I/O multiplexing, signal‑driven, and asynchronous—explaining core concepts such as blocking vs non‑blocking calls, synchronous vs asynchronous processing, and detailing each model’s execution phases, advantages, and typical use‑cases.
This article explains the role of the transport layer in the OSI model, compares TCP and UDP protocols, describes socket types and their APIs, clarifies port number usage, and details multiplexing, demultiplexing, and UDP packet structure with checksum calculation.
The article explains low‑level I/O fundamentals—kernel versus user space, blocking (BIO) versus non‑blocking (NIO) models, and the evolution to multiplexing with select, poll, and epoll—showing how these mechanisms address the C10K problem and are exposed in Java through NIO and Netty APIs.
The article outlines four key dimensions for extreme HTTP performance optimization—encoding efficiency, channel utilization, transmission path, and information security—explaining how advances like binary encoding, multiplexed streams, TCP/QUIC tuning, and TLS 1.3 together reduce latency, boost concurrency, and enhance user experience.
The article explains how modern browsers manage TCP connections for HTTP requests, covering persistent connections, the number of requests per connection, pipelining limitations in HTTP/1.1, the advantages of HTTP/2 multiplexing, SSL reuse, and browser-imposed limits on concurrent connections per host.
This article provides a comprehensive overview of the HTTP/2 protocol, explaining its binary framing, multiplexing, header compression, request prioritization, and server push features, and offers step‑by‑step guidance for upgrading Nginx to support HTTP/2 along with detection methods.
The article explains how to select and design disaster‑recovery communication links by evaluating distance, bandwidth, transmission media, and multiplexing techniques such as DWDM, FDM, and TDM, while balancing cost, reliability, and application requirements.
The article explains how modern browsers handle TCP connections and HTTP requests—including persistent connections, the limits on simultaneous connections per host, the (disabled) HTTP/1.1 pipelining, SSL reuse, and how HTTP/2 multiplexing improves image loading performance.
HTTP/2, the first major update to HTTP since 1.1, introduces binary framing, multiplexing, server push, and header compression, dramatically improving web performance by reducing latency, consolidating connections, and optimizing resource delivery, as detailed in this comprehensive overview.
This article explains how traditional per‑connection thread handling (blocking I/O) wastes resources, then demonstrates Java NIO multiplexing and AIO callbacks with complete code examples, showing how they reduce thread usage and eliminate blocking while processing many simultaneous socket connections.
An in‑depth guide walks through HTTP/2 fundamentals—binary framing, streams, messages, and frames—detailing each frame type (DATA, HEADERS, PRIORITY, etc.), Go’s implementation nuances, multiplexing benefits, and practical examples, helping developers harness HTTP/2’s performance gains.
This article provides a comprehensive overview of HTTP/2, explaining its binary framing, multiplexing, and the various frame types such as DATA, HEADERS, PRIORITY, RST_STREAM, SETTINGS, PUSH_PROMISE, PING, GOAWAY, WINDOW_UPDATE, and CONTINUATION, with specific focus on how Go's HTTP server implements these features.
This article explains the limitations of single‑connection request handling, demonstrates the performance benefits of multiplexing, and details a .NET Core test that reaches a million requests per second with low latency using Protobuf messages and BeetleX integration.
This article provides a detailed technical guide on selecting and designing disaster‑recovery communication links, covering distance and bandwidth requirements, fiber types, multiplexing methods, and cost‑effective solutions such as DWDM, SDH, and Ethernet‑based connections.
This article compares HTTP/2 with its predecessor HTTP/1.x, detailing performance gains through multiplexing, binary framing, header compression, and server push, and explains the underlying mechanisms such as TCP behavior, binary frames, static and dynamic header tables, illustrating concepts with visual examples.
HTTP/2, the modern successor to HTTP/1.1, introduces binary framing, header compression, multiplexing, server push, and other enhancements that dramatically reduce latency and improve efficiency, making web pages load faster and more reliably across browsers and servers that support the protocol.
This article examines how widespread HTTP/2 adoption changes front‑end architecture, demonstrates concrete speed improvements through multiplexing, priority, and server‑push with real‑world demos and HAR analysis, and explains which legacy optimizations become obsolete.
This article explains the key innovations of HTTP/2—including binary framing, multiplexing, header compression, request priority, server push, and flow control—while also providing practical tools and experimental results that demonstrate its performance advantages over HTTP/1.1 and SPDY.
This article explains how HTTP/2 replaces SPDY, introduces multiplexing, header compression and Server Push, and shows why many HTTP/1 optimization tricks become obsolete while still offering practical strategies for faster resource loading on modern web pages.
