5 ms·

Man, I’m just waiting for AWS load balancers to support HTTP2. Last time I checked they still convert HTTP2 into HTTP1 for downstream endpoints.

• dochtman 7y ago
  Why is that an issue for you? It seems like the downstream connection would be on AWS' internal network, so HTTP 2 doesn't have as many advantages.
  • halfdan 7y ago
    HTTP/2 push comes to mind. Your services hosted behind an ALB won't be able to make us of it if the connection is dropped to HTTP/1.1
  • jdub 7y ago
    It's not just the performance – it'd be nice if backends could take advantage of the fun new features like push, stream prio, etc. (Though with HTTP/3 around the corner, I can't imagine anyone will bother working on HTTP/2 to backends.)
  • jontro 7y ago
    Hard to support grpc without it
  • rumanator 7y ago
    > so HTTP 2 doesn't have as many advantages. Request pipelining and multiplexing are good enough reasons.
• mekster 7y ago
  Maybe just run your own instance as a load balancer?
  • alex_duf 7y ago
    Running your own load balancer is a non negligeable amount of work for not that much benefit, and hard to nail if you're operating at scale. "Just" seems like an understatement here, there's a reason why ELBs and ALBs are popular solutions.
  • snypox 7y ago
    Not an option.