--- title: GRPC Reviews meta_title: 'GRPC Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 23 reviews by the users' company size, role or industry to find out how GRPC works for a business like yours. aggregate_rating: rating_value: 4.3 review_count: 23 scale: '5' date_modified: '2026-06-21' parent_category: name: Containerization url: https://www.g2.com/categories/containerization --- # GRPC Reviews **Vendor:** GRPC **Category:** [Service Discovery Software](https://www.g2.com/categories/service-discovery) **Average Rating:** 4.3/5.0 **Total Reviews:** 23 ## About GRPC GRPC is a high performance, open source, general RPC framework based on HTTP/2. ## GRPC Reviews ### 1. Communication is much faster as compared to the http request **Rating:** 3.0/5.0 stars **Reviewed by:** Saurabh kr. G. | Senior Software Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** December 01, 2022 **What do you like best about 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 **What do you dislike about GRPC?** 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. **What problems is GRPC solving and how is that benefiting you?** It is providing much faster communication as compared to the normal http request. Almost 6-7 times faster in processing the request and return response. Yes performance is much more increased. ### 2. is good **Rating:** 2.5/5.0 stars **Reviewed by:** Verified User in Telecommunications | Small-Business (50 or fewer emp.) **Reviewed Date:** October 02, 2023 **What do you like best about GRPC?** language independent, converssion to prototype is easy **What do you dislike about GRPC?** idls do not allow function defn, build procedure is nott claar **What problems is GRPC solving and how is that benefiting you?** general remote procedure caling ### 3. gRPC - the best APIs - and works great with protobuf **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Marketing and Advertising | Enterprise (> 1000 emp.) **Reviewed Date:** May 15, 2023 **What do you like best about GRPC?** * APIs with types * Streaming APIs * Tight integration with protobuf These are all great reasons to be a big fan of gRPC! **What do you dislike about GRPC?** 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. **What problems is GRPC solving and how is that benefiting you?** gRPC is a great way for us to interact with APIs, connect services, and in general have better and more performant systems than we were able to have with just REST and JSON. ### 4. GRPC - The goto communication library **Rating:** 4.5/5.0 stars **Reviewed by:** Vishal M. | Technical Lead, Mid-Market (51-1000 emp.) **Reviewed Date:** September 01, 2022 **What do you like best about GRPC?** 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. **What do you dislike about GRPC?** 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 **What problems is GRPC solving and how is that benefiting you?** GRPC helps resolve the communication among the micro service based environment very easy, scalable and convenient. It also supports streaming of data which helps greatly for streaming based apps like mp3, videos ### 5. Effective and efficient api service. **Rating:** 5.0/5.0 stars **Reviewed by:** rutika a. | Budget analyst, marketing specialist, Small-Business (50 or fewer emp.) **Reviewed Date:** March 11, 2022 **What do you like best about GRPC?** It is fast, effective and efficient framework.it provide developed environment to work into. **What do you dislike about GRPC?** Everything is good accept the updated part notification Due to some bug. Otherwise its a good work experience. **What problems is GRPC solving and how is that benefiting you?** Due to the heavy communication between the clients it helped me a lot in effective communication. Also faced API efficacy problem. It also helped me to overcome this problem with gRPC. ### 6. GRPC for Polyglot implementation **Rating:** 3.5/5.0 stars **Reviewed by:** Shriya S. | Specialist Programmer, Small-Business (50 or fewer emp.) **Reviewed Date:** August 30, 2021 **What do you like best about GRPC?** 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 **What do you dislike about GRPC?** 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. **What problems is GRPC solving and how is that benefiting you?** 1. Supports polyglot implementation For Example: Without GRPC: A client library on C# build their own application and their server (let suppose nodejs ) is a REST API and they start building. But now they want server to upgrade to HTTP 2 and their client library is build by someone who decided no longer to maintain it. Now you have to use HTTP 1 and not take advantage of HTTP 2 But if you have browser then browser maintains client library . But if you build a Python, Java, NodeJS application then there is a problem. GRPC solves this problem, client and server can be written in separate languages. 2. Internally uses HTTP2, hence more performant 3. Progress Feedback (upload feature ) can be implemented easily. 4. Compact:We are send binary data through a wire instead of a JSON object. 5. Proto buffer: Reduces payload size ### 7. Well its just great when we want to work with distributed system. **Rating:** 4.0/5.0 stars **Reviewed by:** Prashant K. | Resident software engineering intern, Small-Business (50 or fewer emp.) **Reviewed Date:** March 11, 2022 **What do you like best about GRPC?** Faster , lightweight and much efficient then REST which makes it more lovable. **What do you dislike about GRPC?** obvious one is weak ecosystem not many dev uses it, and less browser support **What problems is GRPC solving and how is that benefiting you?** in distributed systems , there can have multiple languages and tech and to make it work together grpc greatly help. ### 8. gRPC is awesome and we are consistently trying figure out a complete ecosystem for working with it **Rating:** 5.0/5.0 stars **Reviewed by:** Raveesh A. | Engineering Manager (Mobile), Small-Business (50 or fewer emp.) **Reviewed Date:** August 08, 2021 **What do you like best about GRPC?** 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. **What do you dislike about GRPC?** 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 **Recommendations to others considering GRPC:** go for it **What problems is GRPC solving and how is that benefiting you?** The main benefit of gRPC is when building isolated systems with multiple teams that need to collaborate with one common backend/central system. To have specs enforced by gRPC we can ensure that there is one single source of compute for the whole ecosystem ### 9. blazing fast & efficient api service **Rating:** 4.5/5.0 stars **Reviewed by:** Md Mahabub A. | Software Development Engineer IV, Small-Business (50 or fewer emp.) **Reviewed Date:** September 08, 2021 **What do you like best about GRPC?** 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. **What do you dislike about GRPC?** 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. **What problems is GRPC solving and how is that benefiting you?** long-lived and real-time communication problems. API efficiency problem. All can be solved with gRPC. ### 10. GRPC is just the best way to do communication in complex systems **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** September 07, 2021 **What do you like best about GRPC?** The abstraction that it provides when it comes to planning the different components that will communicate with eachother **What do you dislike about GRPC?** 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) **What problems is GRPC solving and how is that benefiting you?** In the VoIP sector, there are a lot of communication between different systems that don't necessarily speak the same language and having GRPC has made it very easy to overcome this. ### 11. Grpc review **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Telecommunications | Small-Business (50 or fewer emp.) **Reviewed Date:** August 26, 2021 **What do you like best about GRPC?** 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 **What do you dislike about GRPC?** Changing IDL(interface defination language) protocol buffer from time to time as the services evolove could be worrying for the developer(could be automated) **What problems is GRPC solving and how is that benefiting you?** With this framework we are able to make 2 way communication between client and server Harnessing the power of Http 2.0 protocol Securing the data sent over the network as it is transferred in binary. ### 12. I have gone through the product, It is nice **Rating:** 5.0/5.0 stars **Reviewed by:** Mirtunjay K. | Site Reliability Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** August 07, 2021 **What do you like best about GRPC?** Easy to get started, easy to implement and their documentation is neat and clean **What do you dislike about GRPC?** Still not yet founded since the product is good, I'll update if it is **Recommendations to others considering GRPC:** Anyone wants to implement them just go through the documentation and you will have all your answeres **What problems is GRPC solving and how is that benefiting you?** Since it is opensource, there is more way anyone can utilize ### 13. GRPC is the Lightweight secure API. **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** September 18, 2021 **What do you like best about GRPC?** . 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. **What do you dislike about GRPC?** Less opensource tools available like postman... **Recommendations to others considering GRPC:** Please use it and try it out. **What problems is GRPC solving and how is that benefiting you?** Implementing backend servers and solving a lot of customer problems and helps in scalability nd bidirectional streaming services and it is more reactive. ### 14. GRPC, great protocol to communicate between microservices **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** August 17, 2021 **What do you like best about GRPC?** GRPC is a great protocol to communicate between two micro-services. It can easily be developed and had great documentation for all the languages. It also has provided examples for implementing it. It is very fast and does byte calls in miliseconds. **What do you dislike about GRPC?** There is nothing to dislike about it. You will love everything about GRPC. **What problems is GRPC solving and how is that benefiting you?** We are using GRPC to communicate between our micro-services. It has helped us to communicate very faster and effective way. ### 15. Great Service. **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Small-Business (50 or fewer emp.) **Reviewed Date:** October 19, 2021 **What do you like best about GRPC?** Helps in making quicker and better decisions. **What do you dislike about GRPC?** Nothing as of now, I would be able to provide more details once we dig into the service more. **What problems is GRPC solving and how is that benefiting you?** Building out of the box and cutting edge streaming services. ### 16. gRPC the new era of APIs **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** September 08, 2021 **What do you like best about GRPC?** Streaming and http2 support. Security and middleware support **What do you dislike about GRPC?** Tooling support like postman is not there **What problems is GRPC solving and how is that benefiting you?** The API contract is much more stable and you can auto-generate gRPC proto code. ### 17. bare minimum code, highly efficient **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.) **Reviewed Date:** September 09, 2021 **What do you like best about GRPC?** bare minimum lie of code low latency highly effcient **What do you dislike about GRPC?** bit complex to understand and start for new developers **What problems is GRPC solving and how is that benefiting you?** using for interservice communication using in various order processing flows using various mobile device communications to send the updates on order processing ### 18. Worth but complex **Rating:** 3.5/5.0 stars **Reviewed by:** Bharani kumar Y. | Infrastructure Developer, Mid-Market (51-1000 emp.) **Reviewed Date:** August 11, 2021 **What do you like best about GRPC?** Cross platform functionality, fast and efficient **What do you dislike about GRPC?** More complex structure, Harder for large API's **What problems is GRPC solving and how is that benefiting you?** Application development ### 19. Grpc is great **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** August 27, 2021 **What do you like best about GRPC?** Easy to use, fast and great documentation **What do you dislike about GRPC?** NodeJS grpc version does not work with certain libaries (Any datatype) **What problems is GRPC solving and how is that benefiting you?** Avoids the hassle of creating language unique apis to communicate with out product. ### 20. Review GRPC **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Higher Education | Small-Business (50 or fewer emp.) **Reviewed Date:** August 29, 2021 **What do you like best about GRPC?** Makes use of HTTP2 protocol and language flexible. **What do you dislike about GRPC?** litttle bit difficult to understand for Novice developers. **What problems is GRPC solving and how is that benefiting you?** Worked on some basic projects. So it is difficult to say . ### 21. GRPC recommendation **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Program Development | Small-Business (50 or fewer emp.) **Reviewed Date:** August 10, 2021 **What do you like best about GRPC?** I mostly like the speed of grpc, which is 7 to 10 times faster than REST. **What do you dislike about GRPC?** There are not many resources for the GRPC. **Recommendations to others considering GRPC:** Just go for it **What problems is GRPC solving and how is that benefiting you?** I want to make a backend with grpc. ### 22. Performance for your apis **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** August 17, 2018 **What do you like best about GRPC?** The binary protocol allows you to define apis that have a high amount of data load in a performant way. It is possible to integrate it with most of the modern lprogramming languages **What do you dislike about GRPC?** It still doesn’t support dynamic proto definition parsing in languages different than c, and that’s a really useful feature. It can also be a bit hard to deeply understand because of it’s internal complexity **What problems is GRPC solving and how is that benefiting you?** High data voulme apis like an ingestion service for a big data pipeline, it is way more performant than rest services for this purpose ### 23. Joyful experience all over the stack **Rating:** 5.0/5.0 stars **Reviewed by:** Toby A. | Developer, Small-Business (50 or fewer emp.) **Reviewed Date:** October 24, 2017 **What do you like best about GRPC?** Incredibly nice and easy to implement in your services, and gives you nothing but benefits - from tooling, to network optimizations. gRPC really shines where you have a polyglot backend, as you're freely able to distribute a spec for how these microservices are to interact together. And using the great tooling, you can generate a lot of the code for your desired language. **What do you dislike about GRPC?** Some of the language-specific tooling has its downsides - but it's never too bad. **What problems is GRPC solving and how is that benefiting you?** gRPC allowed us to save on latency and bandwidth for internal services. It also frees up the ability to use the correct language for the correct service, as you can generate a lot of boilerplate code using gRPC's tooling. ## GRPC Discussions - [Is gRPC a framework?](https://www.g2.com/discussions/is-grpc-a-framework) - 1 comment - [View GRPC pricing details and edition comparison](https://www.g2.com/products/grpc/reviews?section=pricing&secure%5Bexpires_at%5D=2026-06-24+23%3A33%3A03+-0500&secure%5Bsession_id%5D=8560b39d-de80-4d10-9c49-dd499d9c53f8&secure%5Btoken%5D=c95d5672e02bddee3aa4155a9d65b11954b0e714d83e6623d7ee234c28ca0442&format=llm_user) ## Top GRPC Alternatives - [Apache Thrift](https://www.g2.com/products/apache-thrift/reviews) - 4.1/5.0 (22 reviews) - [Docker](https://www.g2.com/products/docker-inc-docker/reviews) - 4.6/5.0 (289 reviews) - [ZooKeeper](https://www.g2.com/products/zookeeper/reviews) - 4.3/5.0 (87 reviews)