0 views collected around this technical thread.
This article traces the evolution from HTTP/1.1 to HTTP/3, explains QUIC's design and its advantages over TCP, and examines how features like connection migration, head‑of‑line blocking elimination, congestion control, and flow control improve latency and reliability for modern web applications.
ROFF is a Rust‑implemented, seven‑layer gateway that delivers high‑throughput load balancing with memory‑safe performance, TLS hardware offload, native QUIC/HTTP3 support, a hot‑reload/upgrade mechanism, and an extensible module system allowing over thirty built‑in filters and custom Rust macros.
The article provides a comprehensive technical overview of HTTP's history, the design and advantages of the QUIC protocol—including connection establishment, migration, head‑of‑line blocking mitigation, congestion control, ACK handling, and stream/connection flow control—while contrasting it with TCP and HTTP/2 mechanisms.
This article reviews the evolution of HTTP from its early versions to HTTP/3, explains the QUIC protocol and its advantages over TCP, and discusses connection establishment, migration, head‑of‑line blocking, congestion control, and flow control mechanisms that improve modern web performance.
This article traces the evolution of HTTP from its 1991 inception through HTTP/1.1, HTTP/2, and HTTP/3, explains the QUIC protocol’s design and advantages, and details connection establishment, congestion control, flow control, and head‑of‑line blocking mitigation techniques used in modern web transport.
The team built a reusable low‑latency live‑streaming platform for the European Cup that replaces HLS with RTMP over QUIC, reuses VOD bandwidth, automates stream control, and cuts playback latency by 20 seconds while dramatically lowering bandwidth costs and delivering stable 1080p 50 fps HDR video.
This article details the deployment of QUIC in Trip.com’s mobile app, covering multi‑process architecture, containerized upgrades, service discovery, health monitoring, push‑pull resilience, full‑link tracing, congestion‑control algorithm redesign, and the resulting performance and reliability improvements achieved across global users.
This article explains the evolution of HTTP from 1.1 to HTTP/3, introduces the QUIC protocol and its packet‑based design, and details how QUIC reduces RTT, solves head‑of‑line blocking, improves congestion and flow control, and supports connection migration.
This article explains the evolution from HTTP/1.1 to HTTP/3, detailing QUIC's UDP‑based design, its impact on connection establishment, migration, head‑of‑line blocking, multiplexing, congestion control, forward error correction, and flow‑control mechanisms for modern web services.
QDSR is a high‑performance QUIC traffic‑forwarding framework that integrates Direct Server Return to remove redundant downstream forwarding in layer‑7 load balancers, allowing multiple real servers to stream data directly to clients via a one‑way tunnel, achieving up to 12.2× higher throughput and significantly lower latency while preserving security and connection consistency.
BiliBili created the proprietary BMT (Bili Media Transport) streaming protocol, which consolidates FLV and HLS delivery into a low‑overhead, multi‑track, codec‑agnostic format using QUIC‑accelerated back‑haul, cutting daily CDN back‑haul traffic by over 100 GB and enabling richer live‑streaming features.
Tencent has open‑sourced TQUIC, a Rust‑based, high‑performance, lightweight cross‑platform QUIC library that supports multiple congestion‑control algorithms, multi‑path networking, and memory‑safe operation, delivering 2‑30% faster transmission and up to 20% higher processing speed while improving latency‑sensitive services such as video, gaming, advertising, and e‑commerce.
Taobao migrated its long‑chain network from a private SlightSSL over HTTP/2 to a full HTTP3/QUIC stack built on the XQUIC library, adding unified TNET interfaces, UDP probing and fallback, which cut recommendation latency by up to 33 %, transaction latency 32 %, boosted upload speed 21 % and short‑video download 18 % while solving UDP port, load‑balancing and kernel memory challenges.
This article details the background, design choices, and concrete implementation of integrating the QUIC protocol into both client and server components, describing multi‑channel management, load balancing, performance gains, and future optimization plans for improving network reliability in diverse overseas environments.
By replacing TCP+TLS with QUIC, Tencent Meeting cuts connection‑setup latency by nearly half, enables seamless Wi‑Fi‑to‑cellular handover through connection migration, improves login success, tolerates high packet loss, and incorporates fallback and crash‑guard mechanisms to ensure reliable video conferencing.
The Vivo Internet Operations team outlines how they cut short‑video startup latency by warming DNS caches, consolidating domains for HTTP/1.1 reuse, deploying HTTP/2 and QUIC, and optimizing CDN edge placement, achieving up to 30 ms DNS gains, 40 ms image load reductions, and lower request and first‑byte latencies.
The article explains how HTTP/3 abandons TCP in favor of the QUIC protocol built on UDP, detailing TCP's head‑of‑line blocking, handshake latency, middlebox rigidity, and how QUIC’s reliability, multiplexing, and fast handshakes address these issues while also noting deployment challenges.
Bilibili’s video CDN replaced its traditional TCP‑based gateway with a QUIC/HTTP‑3 gateway and, to curb the extra CPU load caused by complex UDP handling, adopted AF_XDP kernel‑bypass sockets that redirect packets via XDP, cutting CPU usage by about half, raising peak bandwidth to roughly 9 Gbps and improving per‑bandwidth efficiency by up to 30 %.
This article explains the fundamentals of the HTTP protocol, covering request preparation, message structure, methods, headers, caching, the request/response cycle, HTTP/2 enhancements, and the QUIC protocol's advanced features for faster, more reliable web communication.
To achieve sub‑second start‑up for mobile video streaming, the iQIYI overseas project applies layered HTTPS optimizations—including DNS and certificate caching, ECDHE/X25519 key exchange, false start, lightweight cipher suites, ECDSA certificates, OCSP stapling, and session‑ID/ticket reuse—while transitioning toward TLS 1.3 0‑RTT and HTTP/3 QUIC for further latency reduction.