High-performance web apps using HTTP/2

on YouTube ↗50m

" summary

HTTP/2 replaces text with binary framing and uses multiplexing with one connection per origin so many requests load concurrently (demo: a small image page drops from ~13s on HTTP/1 to ~2s on HTTP/2); it adds HPACK header compression and server push (default max concurrent streams ≈100). Demos use Go, Caddy and Node/Express with Chrome net-internals; server push sometimes wastes bandwidth because servers re-push cached resources and many server implementations don’t suppress redundant pushes. Migration notes: upgrade CDNs, stop domain sharding, re-split bundles.

AI-written summary · about

" chapters (12)

1. 0:00Introduction
2. 2:40What is HTTP/2
3. 6:36Binary protocol basics
4. 11:33Multiplexing and head-of-line blocking
5. 14:28HTTP/1 vs HTTP/2
6. 17:27Header compression & server push
7. 20:43Live demos
8. 30:39Performance limits
9. 37:49Code walkthrough
10. 38:36Migration strategies
11. 43:11Impact on performance
12. 48:36Summary

" related talks

• 01h 00mHTTP/2 - The future of the web todayRob Crowley · NDC Sydney 2017
• 20mA quick primer on http2Cyrus Dasadia · Rootconf 2015
• 43mHTTP 2.0: why and howSimone Bordet · Voxxed Days Ticino 2017
• 03h 16mPUSHing web app performance with HTTP/2Inian Parameshwaran, Sebastiaan Deckers · JSConf.Asia 2018
• 47mHTTP 2.0 from the Developer's ViewpointDave Methvin · NDC Oslo 2016
• 18mThe Route to HTTP/2Karen Farzam · JSConf.Asia 2015
• 01h 00mHTTP/2 : What you need to knowRobert Boedigheimer · NDC Sydney 2016
• 01h 03mWhirlwind tour through the HTTP2 specOle Michaelis · PHP UK Conference 2016