3 ms·

HTTP/QUIC, so no gRPC then? Or is https://github.com/grpc/grpc/issues/19126 https://github.com/grpc/grpc/issues/19126 not the blocker to gRPC over QUIC I though

HTTP/QUIC, so no gRPC then? Or is https://github.com/grpc/grpc/issues/19126 https://github.com/grpc/grpc/issues/19126 not the blocker to gRPC over QUIC I thought it was. I've long wished for QUIC with Nomad! [1] We've always used a weird QUIC-over-TCP multiplexer called yamux. [2] [1] https://github.com/hashicorp/nomad/issues/23848 https://github.com/hashicorp/nomad/issues/23848 [2] https://github.com/hashicorp/yamux https://github.com/hashicorp/yamux (I'm fairly certain libp2p's fork is actually better)

kingcauchy 7mo ago
Fascinating! We settled on Quic with Protobuf because it was more performant in our testing than the gRPC when coupled with the backoff, failure cases (node startup ordering server/client connections), and to not be coupled with the gRPC library versions in Go, which has bitten us a number of times when dealing with dependency management when you're trying to juggle k8s, etcd, and google dependencies in the same Go project. Plus the performance bottleneck in most of the use cases we're specializing in are on the embedding/ml side of things. Thanks for the links! I hadn't seem yamux before!