gRPC with Protobuf has clear winning and pros and the most importantly easy and fun to write and scale
- HTTP/2 vs. HTTP 1.1
- Messages vs. Resources and Verbs
- The gRPC Gateway. Server 2 Server (S2S) calls in mind- gRPC is way to go. Browser support is not as mature. gRPC is mainly used primarily for internal services that are not exposed directly to the world. Exposing that big workflow for your order, warehouse, async jobs management as API service and RPC call scripted using gRPC is way to go
- Streaming vs. Request-Response. Try built-in health check streaming service and understand the use case. Ever wanted S2S streaming w/o browser involved, this is the solution.
- Bored of too much REST ?? ;)
Weird to see videos on youtube (to promote grpc) talking about REST API is hard to write and the solution being gRPC . Even for an S2S communication REST API client server communication is good . Why gRPC ??