Протокол QUIC и замена TCP

Уровень 0 · материалов: 6

В кластер входят документы, описывающие переход от TCP к UDP-ориентированным решениям (в частности, QUIC и HTTP/3) для повышения производительности сети, и не входят документы, не касающиеся механизмов транспортного уровня.

Общие признаки: замена TCP на UDP, протокол QUIC, снижение задержек (latency), устранение блокировки начала очереди (Head-of-Line blocking), оптимизация транспортного уровня

Группа выше: TCP, HTTP и транспортные протоколы

Материалы

• #19617 — The Evolution of HTTP and the Rise of HTTP/3 — Представитель этого кластера

  HTTP/3: разрушение основ и дивный новый мир — ypastushenko

  Смысл: The main idea is that HTTP/3 solves the fundamental performance limitations of TCP (specifically head-of-line blocking) by moving the transport logic to the application level via the QUIC protocol over UDP, thereby reducing latency and increasing reliability in modern network conditions.

  HTTP/3 replaces the TCP-based transport of previous versions with QUIC over UDP to eliminate head-of-line blocking and reduce connection latency.

• #23547 — HTTP/3 and QUIC: Core Concepts and Evolution

  HTTP/3 от А до Я: основные концепции. Часть 1 — Booka_Ltd

  Смысл: The main idea is that HTTP/3 is essentially a modification of HTTP/2 to work with QUIC, a new transport protocol designed to replace the aging and inflexible TCP. QUIC solves critical issues like Head-of-Line blocking and connection drops during network switches while mandating encryption for better security and easier evolution.

  HTTP/3 is primarily an adaptation of HTTP/2 to run over QUIC, a modern UDP-based transport protocol that fixes TCP's rigidity, reduces latency, and prevents connection breaks during network transitions.

• #12633 — QUIC Protocol: Transitioning the Web from TCP to UDP

  Протокол QUIC: переход Web от TCP к UDP — tangro

  Смысл: The main idea is that the QUIC protocol improves web speed and reliability by moving transport logic from the OS kernel (TCP) to the application layer via UDP, reducing connection latency and solving Head-of-Line blocking.

  QUIC is a Google-developed protocol that uses UDP instead of TCP to drastically reduce connection times, eliminate head-of-line blocking, and allow seamless network switching.

• #1573 — Comparing TCP vs UDP for High-Load Content Delivery

  TCP против UDP или будущее сетевых протоколов — olegbunin

  Смысл: The main idea is that traditional TCP is too rigid and inefficient for modern, unstable mobile networks, and that implementing reliable delivery mechanisms over UDP in user space (as seen with QUIC or custom protocols) allows for significantly better performance, lower latency, and faster iteration.

  TCP is outdated for unstable mobile networks, making reliable UDP-based protocols like QUIC the future for high-performance content delivery.

• #13961 — Optimizing VK Services via QUIC, WebP, and MessagePack

  Как мы отказались от JPEG, JSON, TCP и ускорили ВКонтакте в два раза — alatobol

  Смысл: The main idea is that optimizing the transport and application layers—specifically by replacing outdated protocols (TCP, JSON, JPEG) with modern alternatives (QUIC, MessagePack, WebP)—can drastically improve service performance and business metrics, particularly for mobile users in high-latency environments.

  VK doubled its delivery speed and increased content consumption by replacing JPEG with WebP, JSON with MessagePack, and TCP with QUIC.

• #34107 — UDP Protocol Prototype for Poor Network Conditions

  Делаем мессенджер*, который работает даже в лифте — youROCK

  Смысл: The main idea is that replacing the heavy TCP/IP and HTTP handshake with a streamlined UDP-based approach can significantly improve the reliability and speed of sending short messages in environments with high packet loss and latency.

  The author develops and tests a Go-based UDP prototype to prove that bypassing TCP/IP overhead allows messages to be sent more reliably in poor network conditions like elevators.