2 ms·
> The messages dont work very well with ALB/ELB. Doesn't work on ALB because its HTTP/2 support is trash, not gRPC's fault here. Works fine with NLB btw. > Lo
by dilyevsky 7y ago
> The messages dont work very well with ALB/ELB.
Doesn't work on ALB because its HTTP/2 support is trash, not gRPC's fault here. Works fine with NLB btw.
> Load balancing is done by maintaining multiple connections to all upstreams.
Again, this is a "feature" of HTTP/2. Use linkerd or envoy that support subsetting among other useful things.
Don't blame your misunderstanding of how technology is meant to be used on said technology.
- adamson 7y agoThis feels like a circular argument. Not everyone needs HTTP/2 support (especially for internal services for enterprise applications).
- ptoomey3 7y agoNeed or not need...a bigger issue is simply the technical reality of what you have now. If your non-trivial infrastructure doesn’t have great http2 support, it might be a pretty big lift to make that change first.
- dilyevsky 7y agoYes, it is such a foundational thing that it has to be woven into how you run your infrastructure. Can't just drop it in in most cases. If my memory serves me well, Google basically re-started their entire codebase/infra from scratch - google3 (version 2 was skipped, apparently) to accommodate this shift.