Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Http 2: Should I care?

736 views

Published on

In this talk Sergei Koren, Production Architect at LivePerson will present HTTP/2, the official successor of HTTP 1.1, and how it would influence Web as we know it.

Sergei will talk about:

- HTTP/2 history
- The major changes - what do and don’t
- Expected changes to Web as we use it today
- Proposed checklist for implementation: how and when; from Production point of view.

Published in: Technology
  • Be the first to comment

Http 2: Should I care?

  1. 1. HTTP/2 - Should I care? Sergei Koren (Production Architect)
  2. 2. About myself • Production Architect at Liveperson • 20 years experience as Unix/IT expert • 9 years experience at web companies (LivePerson, eBay, Fraud Sciences) • 3 kids, 2 sport ballroom dancers
  3. 3. Agenda ● What is HTTP/2 ● The major changes - what do’s and dont’s ● Expected changes to Web as we use it today ● Proposed checklist for implementation: how and when; from Production’s point of view
  4. 4. What is HTTP/2 • 2007 - HTTP 1.1 RFC draft. Became de facto standard • … • Feb 2015 - IESG approval for standard • May 2015 - RFC are out!!
  5. 5. HTTP/2 major changes - Don’ts • Same semantics - No need to change Web App • HTTP/1.1 still holds - Browsers with HTTP/2 support initiate connection with HTTP/1.1 (for now) • Same tooling - all modern HTTP clients and servers (will) support it
  6. 6. HTTP/2 major changes - Do’s ● It is Binary - forget “telnet localhost:80, GET /” ● It is framed - one connection - mixed content ● It is encrypted - Encryption is not mandatory by standard, but enforced by some major Clients (Firefox, Chrome) ● Now header is compressed too (new compression algorithm HPACK) ● Server push is now part of protocol ● HTTP/2 kills SPDY
  7. 7. Demo
  8. 8. Expected changes to Web as we use it today Service Delivery Service Development HW resources BAD Speed Good Debugging Security Manageability Complexity Risk New possibilities
  9. 9. Proposed checklist for implementation Criteria Status Tooling support java ✕ - Q4 2016 curl ✓ - last week Browsers ✓ - Most modern Mobile ✕✓ - IOS9? web servers ✕✓ Nginx - end of 2015 Immediate benefit for customer e-commerce/news/blog web ✓ Corporate web/intranet ☓ Web Engagement ✕✓ Behavior browser change (HTTP/2 first, HTTP/1.1 next; HTTP/2 negotiated) ~2018. 2015 for HTTPS
  10. 10. Possible Roadmap for implementation Roadmap Date HTTP/2 exposure by using CDN/Edge HTTP/2 proxy H2 2015 HTTP/2 support on Edge Q1 2016 HTTP/2 on Edge Q2 2016 HTTP/2 backend tuning H2 2016
  11. 11. References ● Ilya Grigorik. Velocity session: “HTTP/2 is here, let’s optimise!” ● Ilya Grigorik, chapter: HTTP/2 A New Excerpt from High Performance Browser Networking ● https://en.wikipedia.org/wiki/HTTP/2 ● http://www.slideshare.net/edburns/http2-comes-to-java-what- servlet-40-means-to-you-devnexus-2015 ● https://www.tollmanz.com/http2-nghttp2-nginx-tls/ ● HTTP/2 implementations ● Performance test comparison ● HTTP/2 site ● Can I use
  12. 12. Wrap up • HTTP/2 has arrived. And it is real • Benefits are clear. There are pitfalls • Know your case, decide carefully
  13. 13. THANK YOU! We are hiring
  14. 14. Some useful info ● HTTP/2 implementations ● Performance test comparison ● HTTP/2 site ● Can I use

×