A Faster Future with HTTP/2

A discussion about the performance improvements and potential performance of HTTP/2. Given at GolangSF in San Francisco on April 22nd, 2015.

Transcript

1. A FASTER FUTURE WITH HTTP/2 By / Engineer @ , Heroku alum Blake Gentry @blakegentry Opendoor GoSF, April 2015
2. HTTP/2 A QUICK INTRO
3. WHY HTTP/2? Performance. End-user perceived latency Network and server resource usage More effective use of bandwidth
4. WHAT DOES HTTP/2 CHANGE?
5. What does HTTP/2 change? WHAT DOES HTTP/2 NOT CHANGE?
6. HTTP/2 IS JUST LIKE HTTP/1.1* *SEMANTICALLY
7. STUFF THAT DOESNT CHANGE Request methods Status codes URLs Other HTTP paradigms
8. HTTP/2 == A NEW BINARY FRAMING LAYER FOR HTTP
9. HTTP/2: MAIN IMPROVEMENTS Multiplexed streams (requests & responses) Header compression (HPACK) Secure TLS required-ish Less optional parts
10. DOES IT MATTER?
11. HTTP/2: ALL-NEW FEATURES
12. GRACEFUL SHUTDOWN Peer can stop accepting new streams, yet finish old ones Enabled by the G O A W A Y frame Peer can stop accepting new streams, yet finish old ones Can be sent by either client or server Includes ID of last processed stream
13. SERVER PUSH “Here, you'll need this too”
14. STREAM PRIORITY Prioritize more important data streams DEPENDENCIES “B depends on A” WEIGHT “C is ½ as important as A”
15. FLOW CONTROL Permission to send more data Credit-based scheme, 65k default Per-connection, and per-stream Applies only to DATA frames (message bodies)
16. STREAM RESET “j/k, I don't need that” Cancel requests or pushes
17. CHALLENGES
18. HTTP/1.1 OPTIMIZATIONS HARMFUL TO HTTP/2 PERF Domain sharding Image sprites Inlining Asset concatenation
19. OPTIMIZE FOR HTTP/1.1 OR HTTP/2? Decide when to switch OR optimize for both at the same time
20. HTTP/2 IS ALREADY HERE! >9% usage in Firefox ( ) source Browser adoption will be extremely rapid.
21. PUSH IS AWESOME, I'M GOING TO USE IT FOR EVERYTHING!
22. SERVER PUSH NOT AS SIMPLE AS IT SEEMS When do we push? Which resources are needed? Does the client already have it cached? How to combine with resource hints?
23. SERVER PUSH WHAT ELSE CAN WE PUSH? On 3XX, push the new resource Push additional API responses Push API dependencies for front-end apps ?
24. STREAM PRIORITY What combination of weights and dependencies is optimal?
25. HOW CAN WE MAKE THIS EASIER?
26. WEB PERFORMANCE IS ALREADY COMPLICATED.
27. THE GOOD NEWS: HTTP/2 GIVES US A LOT FOR FREE
28. THE BAD NEWS: GETTING THE MOST OUT OF HTTP/2 WON'T BE EASY
29. IF PERFORMANCE MATTERS, YOU CAN'T IGNORE HTTP/2
30. LET'S MAKE IT EASIER.
31. CDNs or reverse proxies that make these decisions for you Packages to figure out which resources should be pushed …or track which have already been pushed Perf. testing to determine optimal priorities …or which other optimizations are worthwhile
32. GO IS THE PERFECT LANGUAGE FOR THIS
33. WE'RE HIRING: Front-end Engineers (Angular) Data Engineers Data Scientists
34. THANKS! Blake Gentry / @blakegentry
35. REFERENCES , HTTP/2 Draft 17 HPACK Draft 11 HTTP/2 home page SPDY Whitepaper HTTP/2 Explained bradfitz/http2