3 ms·
This is one of the strengths of gRPC, it forces and centralizes the (mostly type safe) API design from the get-go. Also tends to use a lot less bandwidth.
by pphysch 4y ago
This is one of the strengths of gRPC, it forces and centralizes the (mostly type safe) API design from the get-go.
Also tends to use a lot less bandwidth.
- withinboredom 4y agoThe biggest issue with GRPC is that it is only suitable for stateful languages (iow, languages that can hold values and share them between requests). GRPC is basically worthless for stateless languages and unusable. These stateless languages also don’t work well for websockets either, so it is what it is. Until they solve the stateful part, I’m not using it or recommending it to be used anywhere. Bandwidth is cheap, type safety is overrated, and compute is expensive.