I'm not sure if you mean "can [gRPC] be replaced by REST" or "can [gRPC] replace REST", but my answer in both cases is no. The philosophy of gRPC, or any other RPC protocol, by the way, is to trigger actions on a remote machine, while the philosophy of REST is to access resources in a remote machine.
Some times your domain can be modelled better by resources that are accessed and modified, and some times it works better with actions that are triggered.
The thing is, both RPC and REST have their merits, are useful in different circumstances, and neither is going away anytime soon.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not sure if you mean "can [gRPC] be replaced by REST" or "can [gRPC] replace REST", but my answer in both cases is no. The philosophy of gRPC, or any other RPC protocol, by the way, is to trigger actions on a remote machine, while the philosophy of REST is to access resources in a remote machine.
Some times your domain can be modelled better by resources that are accessed and modified, and some times it works better with actions that are triggered.
The thing is, both RPC and REST have their merits, are useful in different circumstances, and neither is going away anytime soon.