Support http/2

Description

Currently all our resources are served with http/1.1 via nginx to our clients. While we've been vigilant about keeping the number of http connections to a minimum, we also have hard tradeoffs to make: more in a REST request vs. more requests, everything in one ever-growing SPA or more SPAs, etc.

HTTP/2 promises to alleviate some of the need to make these tradeoffs by: binary, multiplexing connections and header compression.

AC:

  • Enable HTTP/2 in Nginx

  • Update Nginx to the latest if possible.

  • Post results of before/after for some normal workflow.

Blocker: This won't work with ELB normally. We have a few options:

  • Use an ALB:

  • Use TCP-mode in the ELB port forwarding (currently in HTTP)

  • Use CloudFront or something similar.

Status

Assignee

Unassigned

Reporter

Josh Zamor

Labels

Components

Priority

Minor