Does HTTP/2 need to be implemented end-to-end to be useful?

Viewed 1147

How much of the performance benefit of HTTP/2 is lost if only the client <-> load balancer is HTTP/2 and the actual web server isn't? I'm guessing it depends on the latency and bandwidth between the load balancer and the server, but if you had to guesstimate for the average case, would it matter at all?

2 Answers

We have managed to support HTTP/1.1 & HTTP/2 end-to-end using AWS ALB and 2 target groups. First one is routing user-agents which are common browsers to target group communicating over HTTP/2 and a fallback target group communicating over HTTP/1.1

I hope this may help someone as we have spent days trying to figure out how to do end-to-end HTTP/2 for our web app behind an AWS ALB.

Related