---
title: "Discussion on \"Network Part 3 - How HTTP Outgrew TCP\" | Hashnode"
description: "Discussion on \"Network Part 3 - How HTTP Outgrew TCP\". From HOL Blocking to QUIC — how HTTP/1.1, HTTP/2, and HTTP/3 each made a different call on what to keep and what to let go, read through Path Dependency and the Innovator's Dilemma."
url: "https://hashnode.com/posts/network-part-3-how-http-outgrew-tcp/6a01df77fca21b0d4b2b3732"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Network Part 3 - How HTTP Outgrew TCP](https://lukyday.hashnode.dev/network-part-3-how-http-outgrew-tcp?utm_source=hashnode&utm_medium=feed)

From HOL Blocking to QUIC — how HTTP/1.1, HTTP/2, and HTTP/3 each made a different call on what to keep and what to let go, read through Path Dependency and the Innovator's Dilemma.

May 11 · 8 min read · lukyday.hashnode.dev  
Read the article

-   [#networking](https://hashnode.com/tag/networking)
-   [#network](https://hashnode.com/tag/network)
-   [#backend](https://hashnode.com/tag/backend)
-   [#http](https://hashnode.com/tag/http)
-   [#tcp](https://hashnode.com/tag/tcp)

## Written by

[Dayul Lee](https://hashnode.com/@dayul)

@dayul · Seoul, South Korea

  
[View profile](https://hashnode.com/@dayul)

Management informs. Engineering decides. Code is strategy. Every architecture decision has a reason.

Backend engineer with a foundation in distributed systems and high-concurrency architecture. I design real-time, fault-tolerant systems using Java, Go, Kafka, gRPC, and Redis — with a focus on data integrity under load. I document this philosophy in my technical blog (lukyday-blog.vercel.app), where I publish a series titled "Large-Scale Processing" — engineering decisions explained through the lens of business strategy.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.