Embrace HTTP/2 Server Push
H2 brings with it a number of features for improving performance: header compression, request multiplexing, shared compression context.
However, I'd like to focus in on one feature in particular, and how it can make a difference for you: server push.
Server push is a protocol-level feature that allows your server to send additional assets to the client in response to a request. Client asks for A, server knows the client needs B and C as well, the client gets A B and C. Strategically used, this will allow your server to short-circuit the back-and-forth “waterfall” of requests.
This technology has a number of significant implications.
HTTP/1.1 has been in use for over twenty years. That's the era of Netscape 2.0, IE 2.0, Lynx 2.5 (for you grey beards), and the last episode of The Fresh Prince of Bel-Air. Let's bring our bundling strategies into the 20th century.
In this talk, I will:
- Overview HTTP/2 server push and how it works;
- Walk through an example that contrasts performance of an SPA loaded via HTTP/1.1 vs HTTP/2 with server push;
- Summarize the state of affairs for HTTP/2 support on the server-side; and
- Introduce tools and strategies that can help you take advantage of HTTP/2 server push, without sacrificing the power of your current toolset.