QUIC is supported in Java and in C-core via Cronet.  It is not currently
supported in Go.

I don't believe that we have any benchmarks using QUIC.  In general,
QUIC hasn't been a priority for us.

On Mon, Aug 15, 2022 at 11:40 AM Jiaxin Shan <seedjeff...@gmail.com> wrote:

> Hi community,
>
> I am investigating whether QUIC would be beneficial to RPC frameworks like
> gRPC. I do see some proposal in the community like below but seems there's
> no latest updates then. I am trying to understand the blockers here.
>
> 1. Is there explicit benefit to use RPC over QUIC? especially for micro
> service area.  If so, is there benchmark results or theoretical ideas?
> 2. if #1 is true,  is it because engineer team doesn't have bandwidth for
> the support?
> 3. I searched the last email thread in the group and latest one was Oct,
> 2020, any latest update on QUIC (direction may change a little bit?) since
> it's been 2 years.
>
> 1. custom transports to gRPC-Go: grpc/proposal#103
> <https://github.com/grpc/proposal/pull/103>
> 2. Support gRPC over HTTP/3 grpc/grpc#19126
> <https://github.com/grpc/grpc/issues/19126>
>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/bd55d38a-6094-4913-b328-aafc87d0bc86n%40googlegroups.com
> <https://groups.google.com/d/msgid/grpc-io/bd55d38a-6094-4913-b328-aafc87d0bc86n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Mark D. Roth <r...@google.com>
Software Engineer
Google, Inc.

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAJgPXp4ZEVWu7r9vVKkqSf%2BD504X_MJ6bjY8mDkVFt6daX76iw%40mail.gmail.com.

Reply via email to