6 ms·
HTTP2 on the frontend only though, a bit disappointing
by Touche 9y ago
HTTP2 on the frontend only though, a bit disappointing
- tyingq 9y agoMaybe wise though. Biting off http2 on both sides in a load balancer all at once might not be smart. Especially at the same time as multithreading.
- djsumdog 9y agoI agree. I already offload SSL in HAProxy. I'm sure we'll see HTTP2 for frontend/backend communication eventually down the line, but this is a huge and big first step.
- bedis9 9y agoServer side is on its way for next release, haproxy 1.9.
- latch 9y agoAFAIK, this is true of nginx also and from what I've heard in the past, they see no reason to change it. I can't find it now, but I'm sure they had pretty compelling benchmarks that showed that with keepalive & low-latency networks, performance wise, there's little, if any, performance difference.
- Touche 9y agoThe reason would be so that the backend can take advantage of H2 features.
- thresh 9y ago> AFAIK, this is true of nginx also and from what I've heard in the past, they see no reason to change it. http2 backends support is on the roadmap https://trac.nginx.org/nginx/roadmap https://trac.nginx.org/nginx/roadmap - so you can expect it to be implemented.
- manigandham 9y agoLook at Lyft's Envoy: https://www.envoyproxy.io/ https://www.envoyproxy.io/
- bedis9 9y agoLOL this software does not even understand HTTP/1.0...
- manigandham 9y agoBased on your comments, I assume you're involved with HAProxy? Is HTTP/1.0 (vs 1.1) actually used anywhere? Both versions are also compatible so what's the issue? Also seems rather disingenuous to say "even" when Envoy has plenty of other advanced features.