so gRPC has benefits from performance level due to protobuf encoding; smaller payloads as well as a clear contract which is tangible and not like REST where things are tied together manually (creation of payload, correct URL, query param vs request body)

I'll reply with a follow up on how to integrate it with web, and try to drive the point home that with generated stubs, maintenance becomes so much easier! Stay tuned :)

isn't it easier, as you have now auto-generated stubs for all the available service methods? this will make the integration between backend and frontend super tight - same contract is used to generate the code on both ends, no more searching the correct payload or api endpoint :)

there is with a proxy to patch over the differences and even http1 to http2 Tomas Y. https://github.com/improbable-eng/grpc-web/tree/master/go/grpcwebproxy

Haha, yes I agree there's a bit of ceremony. Generate code and use a grpc-web proxy for the protocol conversions, but overall maintenance wise it will make a lot easier.

It has browser support since 2016, if you check the code link mentioned at the end of the page. You can find the web integrated with gRPC service. bulky-client it doesn't right? It makes you free from manually hand-crafting the http request it generates the stubs only, which know how to connect to the remote service json there's no json, as the client can directly use the response objects created and use it in app no need to know the format of the serialzed data sent over the wire

Congrats everyone. Loved the community support motivating everyone. So many cool submissions 🎉

Thanks so much! 😊

Thank you!

Targeting this month, we'll be friends there 🎉