Tag

#http2

88 posts25 followers

Explore Hashnode

Alternatives

nRouter.aiOct 14 · 3 min read

Reading a Benchmark Table Honestly: TTFT Percentiles From a Warm-Pool Gateway Test

Vendor benchmarks deserve suspicion. Most hide the workload, cherry-pick the tier, or quote a p50 and let you assume the tail behaves. So let's read one the way it should be read — method first, numbe

nrouter.hashnode.dev

Abhijeet ShindeSep 5 · 10 min read

How HTTP Works: What Happens After DNS Hands You an IP

1. Why This Topic Matters The last post ended on a promise: once DNS resolves a name to an IP, what actually happens next? Every post in this series up to now — TCP, UDP, and finally DNS — has been ab

weeklyupdate.hashnode.dev

Bikash ShawAug 21 · 12 min read

Computer Networks #13: HTTP/2: How HTTP Became Faster

In the previous blog, we looked at HTTP/1.1 and one of its biggest limitations: Head-of-Line Blocking. HTTP/1.1 allowed us to reuse the same TCP connection for multiple requests, but it still had limi

backendblogs.hashnode.dev

Anik SikderAug 1 · 8 min read

Multiplexing vs Connection Pooling: Why HTTP/2 Changed Everything

In the previous articles of this series, we explored a recurring theme: Every generation of web infrastructure solved one bottleneck only to expose another. HTTP/1.0 suffered from connection setup ov

aniksikder.hashnode.dev

Oluwaseyi FatunmoleJul 23 · 50 min read

How Clients and Servers Communicate: Full Handbook on HTTP/1.1, HTTP/2, REST, WebSockets, GraphQL, gRPC, and Protocol Buffers

You've built and consumed APIs. You know what a GET request is, what a JSON response looks like, and how to add an Authorization header. You've used REST, maybe tried GraphQL, and perhaps heard of gRP

freecodecamp.org

VignesH KumaRJul 9 · 13 min read

HTTP 103 Early Hints, Explained the Way I Wish Someone Had Explained It to Me

🔍 How I got here I came across HTTP 103 Early Hints while reading about how larger sites shave milliseconds off their load times. The idea is elegant enough to stop and think about: a server usually

happyvig.hashnode.dev

Rahul ChaduvulaMay 30 · 7 min read

Understanding HTTP as a Backend Engineer

After learning about the OSI model, TCP, and UDP, the next thing I wanted to understand was HTTP. As backend engineers, we work with HTTP every day. We build APIs. We send requests. We receive respons

softwareconcepts.hashnode.dev

Doogal SimpsonMar 28 · 5 min read

What About Second HTTP? Solving the 100-File Connection Bottleneck

TL;DR: HTTP/2 replaces the inefficient six-connection limit of HTTP/1.1 with a single, multiplexed stream. By breaking assets into small, interleaved chunks, it eliminates head-of-line blocking and pr

doogal.dev

Oluwatomisin OmotoshoMar 27 · 9 min read

gRPC vs REST in Production

The System That Was Working, until It Wasn't When we started building the backend for a telehealth platform, REST was the obvious choice. We had a handful of services like patient records, scheduling,

oluwatomisin-omotosho.hashnode.dev

Tech Insights HubFeb 12 · 9 min read

HTTP/2 Server Push: Performance Optimization

Why Traditional Server Push Strategies Fail in Modern Environments The original Server Push specification assumed a simpler web architecture. In 2025, several factors make naive implementations problematic: Cache complexity across edge networks: Mode...

topperblog.hashnode.dev

Search Hashnode