Cognitive complexity is a thing. gRPC is nice and all, but how many engineers out there actually fluent in it just like in REST? And remember that this number won't grow unless REST is deprecated which is not going to happen.
Though, gRPC is nice for microservices communication.
what happens if they add support for http3 in the future BOOM, bye bye REST but still it will take time to adapt in the ecosystem
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:
Cons
I believe this is a pretty good piece of technology for microservices intercommunication as it is fast and can reduce the latency in communication.
T.J.
...
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