Reddit’s Move to gRPC

I believe they are also moving their front end to another Google project too <a href="https:&#x2F;&#x2F;lit.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;lit.dev&#x2F;</a> not sure where they are on that.<p>As a side note to the original post, I wish gRPC-web was better supported or alternatively that WebTransport gets standardised quickly. I would love to be able to using gRPC in web apps, it’s such a pleasant experience relative to passing JSON back and forth.

What do folks use to monitor gRPC in production? Every time we think about making the switch, we come up to the lack of protocol documentation and monitoring. Or I missed something obvious which can definitely be the case.

some links for convenience:<p><a href="https:&#x2F;&#x2F;grpc.io&#x2F;about&#x2F;" rel="nofollow">https:&#x2F;&#x2F;grpc.io&#x2F;about&#x2F;</a><p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;GRPC" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;GRPC</a><p>&quot;gRPC (gRPC Remote Procedure Calls[2]) also known as Google Remote Procedure Call is an open source remote procedure call (RPC) system initially developed at Google in 2015.... Most common usage scenarios include connecting services in a microservices style architecture, or connecting mobile device clients to backend services.&quot;<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Remote_procedure_call" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Remote_procedure_call</a>

Is this solely due to HTTP&#x2F;2 support, or are there other good reasons for gRPC?