HTTP/2 is a new version of the HTTP network protocol that improves performance and efficiency over HTTP/1.1. It uses a binary format and multiplexing to allow multiple requests and responses to be delivered over the same connection. HTTP/2 also supports server push, request prioritization, header compression and other features to reduce latency and improve page load times compared to HTTP/1.1. Major browsers and companies like Google and Twitter are implementing HTTP/2, and it is expected to become the new standard for the web.

1. WHY HTTP/2 ?
WHY IS IT SO
COOL ?
CLEMENT DELAFARGUE
@CLEMENTD
2013

2. Clement DELAFARGUE from Clever Cloud
@clementd on twitter – @divarvel on github
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 JOB OF HTTP?

8. THE SPEC IS MADE TO BE
EXTENSIBLE

9. BUT THE INTERNET IS
EVOLVING

10. FASTER FASTER FASTER

11. // REQUESTS ?

12. KEEP-ALIVE?

13. HTTP PIPELINING

14. THE HACKS WE ARE
DOING EVERYDAY
WITHOUT
THINKING IN
ORDER TO IMPROVE
PERFORMANCES

15. MULTIPLE DOMAIN NAMES FOR
MULTIPLE STREAMS

16. STATIC ASSETS DOMAIN NAME FOR FAT
COOKIES PROBLEM MANAGEMENT

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

18. SO, WE NEED A NEW VERSION OF HTTP

19. WHO IS IN CHARGE ?

20. HTTPBIS
WORKING
GROUP

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

22. BUILD ON SOMETHING

23. EVERYBODY IS AT THE TABLE

24. SO WHAT IS IN THE BOX ?

25. HTTP/2 IS A BINARY
PROTOCOL

26. COMPRESSION + SSL UNABLE
TO READ ANYTHING

27. WIRESHARK FOR ALL

28. PUT SOME STEAMS IN ONE
CONNECTION

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

30. STREAMS ARE BUILT
OF FRAMES

31. 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
…

32. BASICALLY
connection
streams
frames

33. BINARY GOODNESS =>
FRAMING IS EASY

34. KILL MULTIPART $*%Ù£
FORMAT

35. PUSH FROM THE SERVER A RESOURCE
TO THE CACHE

36. STREAMS PRIORITY

37. HEADERS
COMPRESSIONS

38. HPACK
*new RFC*

39. HEADERS
PERSISTENCE

40. FOCUS ON WEB
PERFORMANCES

41. TRANSITION

42. URLS
CANNOT
CHANGE

43. HOW TO UPDATE THE
WEB ?

44. HTTP
&
HTTPS

45. NEGOTIATE
A
PROTOCOL
ELEVATION

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

47. WORKFLOW

48. WORKFLOW

49. IT’S STILL SLOW

50. ENCRYPT
THE WEB :
TLS

51. NEGOTIATE
TLS
VERSION
AND
CIPHER…

52. NEGOTIATE THE PROTOCOL AT
THE SAME TIME AS THE
ENCRYPTION NEGOTIATION

53. NPN (CLIENT)
&
ALPN (SERVER)

54. IS IT FOR
REAL?

55. LOOKS LIKE
IP V6
STORY?

56. MORE SPDY STORY

57. DRAFT – 14 / 15
- Firefox
- Chrome
- cURL
- IE (oh yeah)
- …
- Google
- Twitter
- Akamai
- ….

58. BENCH

59. CLEVER CLOUD POV

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

61. ALL THE
GOODNESS OF
HTTP2 IN
YOUR HTTP1
APP FOR FREE
:-)

62. WHY IT’S
SO COOL?

63. PERFORMANCES

64. REMOVE ALL THE SHITTY
HACKS

65. EXPLORE NEW POSSIBILITIES

66. IMPROVE THE USERS XP

67. I’m @clementd on twitter
I’m the CTO of
A PaaS provider, give it a try
;-)
THX FOR LISTENING
& QUESTIONS TIME