Top Rated GRPC Alternatives
* APIs with types
* Streaming APIs
* Tight integration with protobuf
These are all great reasons to be a big fan of gRPC! Review collected by and hosted on G2.com.
I wish gRPC was more commonplace. It is rather easy-to-use once people get moving with it, but it is not commonplace enough across industry, yet. Review collected by and hosted on G2.com.
22 out of 23 Total Reviews for GRPC
It's way to directly used from the compiled Java files generated by the proto files and using them as stub in different microservices. It is much better than the competitors as it is 6-7 times faster in processing the request and returning the response. There are lot of extra efforts for transformation of request and response Review collected by and hosted on G2.com.
Grpc is quite good with the service it provide but there is a lack of proper documentation and community support for this technology. It would be much better if there are more how to guides on it in simpler way step by step because it is difficult to implement than http.also there are lot of extra effort to implement as well. Review collected by and hosted on G2.com.
GRPC helps remove the complexity to deal with the HTTP protocol, further for highly scalable systems we can have streaming functionality which is quite difficult to implement on top of bare HTTP 2.0.
Also the protobuff helps reduce data size and hence faster communication. Review collected by and hosted on G2.com.
GRPC browser support is very long known issue. That is the only reason that is holding back GRPC for its glory over REST, and hence need to expose REST interfaces for public facing API. Hence the extra effort required to adapt HTTP 1.1 to GRPC based is always an overhead Review collected by and hosted on G2.com.
It is fast, effective and efficient framework.it provide developed environment to work into. Review collected by and hosted on G2.com.
Everything is good accept the updated part notification Due to some bug. Otherwise its a good work experience. Review collected by and hosted on G2.com.
The best part I like about GRPC are :
1. Supports polyglot implementation (client and server can be written in separate language )
2. One client Library
3. Fast and Compact Review collected by and hosted on G2.com.
1. No native Browser support: A request in the browser can't be forced to be HTTP2
2. Proxies: Many proxies are not supporting GRPC (nginx supports GRPC)
3. Latest: Less support
4. Schema: Have to maintain a proto file
5. Less Testing tools: Postman does not support. Review collected by and hosted on G2.com.
Faster , lightweight and much efficient then REST which makes it more lovable. Review collected by and hosted on G2.com.
obvious one is weak ecosystem not many dev uses it, and less browser support Review collected by and hosted on G2.com.
The best thing about gRPC for me is cross-team communication barriers are removed with gRPC and the use of proto-file based source generation. We no longer have to get across through multiple KT calls so for a team to scale this is awesome to work with. The added performance among other benefits are just the cherry on top of the cake. Review collected by and hosted on G2.com.
The ecosystem is majorly built around REST APIs, and it isn't easy to find devs comfortable with gRPC. It takes time for figure out SOPs within the organisation but all of these are necessary efforts and more than pay for it down the line. The ecosystem of third-party and open-source plugins for different cases however is just absent and there will be many cases where we might get blocked and have to spend extra time writing compatibility layers or figuring workarounds Review collected by and hosted on G2.com.
gRPC is ridiculously fast and efficient powered by HTTP/2 . Got a requirement for a fast and efficient lightweight API, go for gRPC.
If you are limited on the payload size, protobuff there to rescue. Review collected by and hosted on G2.com.
It gets complicated when requirements are heavy for your API. Protobuff is cool but not human readable due to binary format.
Limited browser support for gRPC is another drawback that is hard to ignore. Review collected by and hosted on G2.com.
The abstraction that it provides when it comes to planning the different components that will communicate with eachother Review collected by and hosted on G2.com.
It doesn't include all the languages in the world (which is understandable since it is still growing!), and sometimes the only way is to go low level to achieve things (which is fine) Review collected by and hosted on G2.com.
GRPC is new defacto standrad for implementing the microservice which will harness the power of HTTP/2 protocol and help in 2 way communication between server and client Review collected by and hosted on G2.com.
Changing IDL(interface defination language) protocol buffer from time to time as the services evolove could be worrying for the developer(could be automated) Review collected by and hosted on G2.com.
