How HTTP already solved all your performance problems 10 years ago
summary
Claim: HTTP/1.1 already supplies the features that cut server work and latency when used correctly. Examples: serving Google‑hosted jQuery with a year expires saves repeated downloads; ETag and If‑None‑Match let clients get 304s so app code avoids heavy rendering; persistent connections reduce TCP handshakes; caching proxies like Varnish or Squid and load balancers (HAProxy) remove requests from app servers. Caveats: sessions or cookies in Vary or stored per‑user kill cacheability. One deployment hits 150,000 requests/min with five app servers.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:44HTTP/1.0 Example
- 5:26Features in HTTP/1.1
- 10:17HTTP/1.1 Caching
- 11:16Expiration
- 14:02Validation
- 21:36Caching Proxy
- 24:45Resources
- 25:24What About Caching?
related talks
43mPerformance in the World of HTTP 2.0
38mHTTP Headers that Make Your Website Go Faster
41mHigh Performance Kick-Ass Web Apps
50mHigh-performance web apps using HTTP/2
39mWith Great Power Comes Great Responsibility - Using HTTP/2 Responsibly
28mHTTP: History and Performance
49mHTTP: History & Performance
52mHTTP and Your Angry Dog