This document discusses HTTP/2 and why it is an improvement over HTTP/1.1. Some key points covered include: - HTTP/2 uses a binary format for faster processing and includes features like header compression, multiplexing of requests over a single connection, and push capabilities from servers. - It was developed by the HTTPbis working group building off the SPDY protocol draft. - HTTP/2 promises performance improvements by removing hacks used in HTTP/1.1 and enabling new possibilities. The author believes it will improve the user experience. - Support is growing among browsers and companies like Google, Twitter, and Akamai. The author's company Clever Cloud is working to support HTTP/2

1. WHY HTTP/2 ?
WHY IS SO
COOL ?
QUENTIN ADAM AT
@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 IS THE HTTP JOB ?

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

9. FASTER FASTER FASTER

10. // REQUESTS ?

11. HTTP PIPELINING

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

13. MULTIPLE DOMAIN NAMES FOR
MULTIPLES STREAMS

14. STATIC ASSETS DOMAIN NAME FOR FAT
COOKIES PROBLEM MANAGEMENT

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

16. SO, WE NEED A NEW VERSION OF HTTP

17. WHO IS IN CHARGE ?

18. HTTPBIS
WORKING
GROUP

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

20. BUILD ON SOMETHING

21. SO WHAT IS IN THE BOX ?

22. HTTP/2 IS A BINARY
PROTOCOL

23. COMPRESSION + SSL UNABLE
TO READ ANYTHING

24. WIRESHARK FOR ALL

25. PUT SOME STEAMS IN ONE
CONNECTION

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

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

28. BINARY GOODNESS =>
FRAMES IS EASY

29. STREAMS PRIORITY

30. PUSH FROM THE SERVER A RESOURCE
TO THE CACHE

31. HEADERS
COMPRESSIONS

32. HPACK
*new RFC*

33. FOCUS ON WEB
PERFORMANCES

34. URL
CANNOT
CHANGE

35. HOW TO UPDATE THE
WEB ?

36. HTTP
&
HTTPS

37. NEGOCIATE
A
PROTOCOL
ELEVATION

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

39. WORKFLOW

40. WORKFLOW

41. IT’S STILL SLOW

42. ENCRYPT
THE WEB :
TLS

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

44. NPN (CLIENT)
&
ALPN (SERVER)

45. IS IT FOR
REAL?

46. LOOKS LIKE
IP V6
STORY?

47. MORE SPDY STORY

48. DRAFT – 14 / 15
- Firefox (next enable by default)
- Chrome (dev)
- cURL
- IE (oh yeah)
- …
- Google
- Twitter
- Akamai
- ….

49. DRAFT – 14 / 15

50. CLEVER CLOUD POV

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

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

53. WHY IT’S
SO COOL?

54. PERFORMANCES

55. REMOVE ALL THE SHITTY
HACKS

56. EXPLORE NEW POSSIBILITIES

57. IMPROVE THE USERS XP

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