4 ms·
Thank you! Do you know why they were looking to replace Stubby with gRPC? It doesn't seem to me that gRPC is quite customizable enough currently to hook in all
by z77dj3kl 5y ago
Thank you! Do you know why they were looking to replace Stubby with gRPC? It doesn't seem to me that gRPC is quite customizable enough currently to hook in all the monitoring and tooling that I imagine Google has.
And yes, the completion queue approach is pretty cumbersome, would be very interesting to see how stubby went about it :P
- rockwotj 5y ago> Do you know why they were looking to replace Stubby? Likely to maintain less code long term. It's nice to have a primative like this open source so you can use it everywhere (even on mobile). I'm not sure about the claim that gRPC isn't customizable enough, I think there are a lot of hooks in place. For example Open Census does a lot of the instrumentation that you get for free at Google with Stubby, but for gRPC: https://opencensus.io/zpages/ https://opencensus.io/zpages/ > How stubby went about it: Stubby is a lot closer to the experimental callback API talked about here: https://github.com/grpc/proposal/pull/180 https://github.com/grpc/proposal/pull/180