---
title: "Comment by Devashish Rana on \"gRPC - the new REST!\" | Hashnode"
description: "This is pretty good. I think as a technology, we should focus on the pros and cons, and why was it introduced. I think it was introduced to keep a single librar"
url: "https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60d9744b703d372ea06c7308"
---

[Discussion](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4)

Comment [gRPC - the new REST!](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4)

[Devashish Rana](https://hashnode.com/@devDeveloper)

[Jun 28, 2021](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60d9744b703d372ea06c7308)

This is pretty good. I think as a technology, we should focus on the pros and cons, and why was it introduced. I think it was introduced to keep a single library for each client and server, so the changes are centralized, unlike REST.

Pros:

1.  It is fast
2.  It uses http2 under the hood
3.  Single library for each client and server maintained by google

Cons

1.  Protobuf makes the client bulky
2.  No direct use of JSON, it won't make sense for the client to know the schema
3.  No browser support YET
4.  It is new and growing
5.  Proxy Support, as any application deployed is not just simple client and server so, the proxy or gateway layer should understand the protocol as well

I believe this is a pretty good piece of technology for microservices intercommunication as it is fast and can reduce the latency in communication.

[Ankeet Maini](https://hashnode.com/@under-engineered)

[Jun 28, 2021](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60d9744b703d372ea06c7308#reply-60d975e1703d372ea06c7324)

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

[Devashish Rana](https://hashnode.com/@devDeveloper)

[Jun 28, 2021](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60d9744b703d372ea06c7308#reply-60d9ac7a703d372ea06c7d11)

it's just my opinion when I think of grpc, I really appreciate your article.

I just compared with the following scenario of the rest

1.  you don't need any schema
2.  you don't have to stay fixed with a schema from the client side.
3.  any HTTP request you send does not need to have a prevalidated schema

In the case of grpc, you will need a proto file for each grpc service you want to call to the backend. **I meant this when I said bulky.**

From Browser support I mean, there is no direct web API that can call the grpc. To call the grpc you will have to follow something like the following

**client -> rest endpoint -> grpc endpoint**

This was the state when I read about this technology and explored it. I will appreciate it if you can add some resources which can contradict the web API issue.

Thanks for a great article. Happy Coding

[Ankeet Maini](https://hashnode.com/@under-engineered)

[Jun 28, 2021](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60d9744b703d372ea06c7308#reply-60d9d94a68364a2e7b2ce930)

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.

[T.J.](https://hashnode.com/@tx0c)

[Jul 9, 2021](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60d9744b703d372ea06c7308#reply-60e79a8f4e18000309d81b60)

-   No browser support ~~YET~~

[Ankeet Maini](https://hashnode.com/@under-engineered)

[Jul 9, 2021](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60d9744b703d372ea06c7308#reply-60e8af528aaa3f019846ce85)

there is with a proxy to patch over the differences and even http1 to http2[Tomas Y.](https://hashnode.com/@tx0c)

[github.com/improbable-eng/grpc-web/tree/master/go…](https://github.com/improbable-eng/grpc-web/tree/master/go/grpcwebproxy)
