---
title: "Comment by T.J. on \"gRPC - the new REST!\" | Hashnode"
description: "you&#39;re saying REST is only http/1 ? That&#39;s not true, the plain text REST protocol is the most futuristic, and no problem working over HTTP/2 or HTTP/3 g"
url: "https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60e798374e18000309d81b28"
---

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

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

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

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

you're saying REST is only http/1 ? That's not true, the plain text REST protocol is the most futuristic, and no problem working over HTTP/2 or HTTP/3

gRPC is only good use as protocols within datacenter between micro-services, never meant to be called in browser to server and is probably never going to gain support in browsers

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

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

so gRPC has benefits from performance level due to protobuf encoding; smaller payloads as well as a clear contract which is tangible and not like REST where things are tied together manually (creation of payload, correct URL, query param vs request body)
