Network Part 3 - The Evolution of HTTP and the Cost of Every Trade-off
HTTP evolved from HTTP/1.1 to HTTP/3 to address performance limitations caused by head-of-line blocking and TCP's strict ordering. HTTP/2 introduced multiplexing but remained constrained by TCP, while HTTP/3 replaced TCP with QUIC over UDP to eliminate blocking at the transport layer. This progression reflects trade-offs between reliability, latency, and complexity in large-scale network systems.
- ▪HTTP/1.1 suffered from head-of-line blocking, where one slow request delayed all others in the queue.
- ▪HTTP/2 enabled multiplexing over a single connection but still faced head-of-line blocking due to TCP's packet ordering requirements.
- ▪HTTP/3 uses QUIC over UDP, allowing independent streams so that packet loss in one stream does not block others.
- ▪Real-time applications like YouTube and Zoom previously adopted UDP for its low-latency benefits despite its lack of built-in reliability.
- ▪The evolution of HTTP illustrates path dependency, where past design choices like reliance on TCP constrained future protocol improvements.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3907102) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Dayul Lee Posted on May 1 • Originally published at lukyday-blog.vercel.app Network Part 3 - The Evolution of HTTP and the Cost of Every Trade-off #largescale #network #backend #http Large-Scale Network (4 Part Series) 1 Network Part 1 - The OSI Model as a Fault Map 2 Network Part 2 - The Cost of a TCP Handshake 3 Network Part 3 - The Evolution of HTTP and the Cost of Every Trade-off 4 Network Part 4 - Where to Split, Why to Read? Published: April 25, 2026 When the past answer…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
