This document discusses the motivation for and benefits of upgrading to HTTP/2. It notes that HTTP/1.1 is a text-based protocol that requires many hacks to improve performance. HTTP/2 addresses this by being a binary protocol that allows placing multiple requests on a single TCP connection using streams with priority. This improves performance by removing hacks and enabling features like server push and header compression. Implementations are available in browsers and servers. Upgrading websites to HTTP/2 provides a better user experience without requiring code changes for many HTTP/1 applications.

1. WHY HTTP/2?
WHY
UPGRADING
THE WEB?
QUENTIN ADAM
@WAXZCE
2013

2. Quentin ADAM from the Clever Cloud
@waxzce on twitter – github- soundcloud – instagram ….
WHO AM I ?

3. MY DAY TO DAY WORK :
CLEVER CLOUD, MAKE YOUR
APP RUN ALL THE TIME

4. And learn a lot of things about your code, apps, and good/bad design…
KEEP YOUR APPS ONLINE. MADE WITH
NODE.JS, SCALA, JAVA, RUBY, PHP,
PYTHON, GO…

5. AND LEARN A LOT OF THINGS ABOUT
YOUR CODE, APPS, AND GOOD/BAD
DESIGN…

6. WHAT’S THE HTTP JOB ?

7. HYPERTEXT
TRANSFERT
PROTOCOL

9. HTTP1 IS TEXT
PROTOCOL

10. REQUEST <-> RESPONSE
MODEL

11. THE 4 PARTS
Verb Resource
Headers
Body
(optional)

12. THE SPEC IS MADE OF OPTIONS
AND ABILITY TO EXTENDS

13. WHAT WAS THE
REQUIREMENTS?

14. FASTER FASTER FASTER

15. // REQUESTS ?

16. HTTP PIPELINING

17. THE HACKS WE
ARE DOING
EVERYDAY
WITHOUT
THINKING TO
IMPROVE
PERFORMANCES

18. MULTIPLE DOMAIN NAMES FOR
MULTIPLES STREAMS

19. STATIC ASSETS DOMAIN NAME FOR FAT
COOKIES PROBLEM MANAGEMENT

20. COMET/WEBSOCKET/PULLING/SERVER
SENT ENVENT… BIDIRECTIONAL DATA
STREAMS HACKS

21. SO, WE NEED A NEW VERSION OF HTTP

22. WHO IS IN CHARGE ?

23. HTTPBIS
WORKING
GROUP

24. FIRST
HTTP/2
DRAFT IS
SPDY/3
DRAFT

25. BUILD ON SOMETHING

26. SO WHAT IS IN THE BOX ?

27. HTTP/2 IS A BINARY
PROTOCOL

28. HHTP/1 + COMPRESSION +
SSL = ~BINARY

29. BINARY PROTOCOL ARE SAFER, EASER
TO PARSE, CONCISE…

30. WIRESHARK FOR ALL

31. WHAT IS WIRESHARK ?
Your app Wireshark System
Network
card

32. BUILD ONLY 1 TCP
CONNECTION

33. PUT SOME STEAMS IN ONE
CONNECTION

34. STREAMS
~ 1 HTTP/1 REQUEST = 1 HTTP/2 STREAM

35. STREAMS ARE BUILT
OF FRAMES

36. FRAMES
Content
a.html #1
Content
dog.gif #1
Content
a.html #2
Content
dog.gif #2
Content
a.html #4
Content
a.html #3
Content
cat.gif #1
Content
dog.gif #4
…

37. BINARY GOODNESS =>
FRAMES IS EASY

38. STREAMS PRIORITY

39. IMPROVE THE BROWSER
WATERFALL WITH STREAM
PRIORITY

40. PUSH FROM THE SERVER A RESOURCE
TO THE CACHE

41. USER XP WILL BE BETTER

42. HEADERS
COMPRESSIONS

43. HPACK
*new RFC*

44. HEADERS
PERSISTENCE

45. FOCUS ON WEB
PERFORMANCES

46. URL
CANNOT
CHANGE

47. HOW TO UPDATE THE
WEB ?

48. HTTP
&
HTTPS

49. NEGOCIATE
A
PROTOCOL
ELEVATION

50. HTTP/1 BUILD IN METHOD
Upgrade:
header
Code 101
Switching

51. WORKFLOW

52. WORKFLOW

53. IT’S STILL SLOW

54. ENCRYPT
THE WEB :
TLS

55. CURRENT NEGOTIATION:
TLS VERSION, CYPHER…

56. NEGOTIATE THE PROTOCOL IN
THE SAME TIME OF ENCRYPT
NEGOTIATION

57. NPN (CLIENT)
&
ALPN (SERVER)

58. IS IT FOR
REAL?

59. LOOKS LIKE
IP V6
STORY?

60. MORE SPDY STORY

61. BENCHMARK
TIME
CAUTION

63. H2O PERFORMANCES

64. H2, H2-14
- Firefox
- Chrome
- cURL
- IE (oh yeah)
- …
- Google
- Twitter
- Akamai
- ….
https://github.com/http2/http2-spec/wiki/Implementations

65. CLEVER CLOUD POV

66. WORKING ON THIS
Client
http2
reverse
proxy
http2
your app
: http1

67. ALL THE
GOODNESS OF
HTTP2 IN
YOUR HTTP1
APP FOR
NOTHING :-)

68. WHY IT’S
SO COOL?

69. PERFORMANCES

70. REMOVE ALL THE SHITTY
HACKS

71. EXPLORE NEW POSSIBILITIES

72. IMPROVE THE USERS XP

73. TODO LIST
• https://http2.github.io/
• Specs
• Implementations
• FAQ
• News
• Hack with node/h2o/Jetty
• Install Wireshark on your laptop

74. I’m @waxzce on twitter
I’m the CEO of
A PaaS provider, give it a try
;-)
THX FOR LISTENING
& QUESTIONS TIME
clever-cloud.com coupon code:
BDX15