Watching this what I understood is if you create s grpc based server/service/api, its only the grpc client who can access. Whereas when you design rest api a lot of client like languages, javascript, jq etc n mainly devices which understand only json can use easily. Remember when we made Web Api over WCF or We service, we told now a refrigerator can talk to a remote APi
Watching this what I understood is if you create s grpc based server/service/api, its only the grpc client who can access. Whereas when you design rest api a lot of client like languages, javascript, jq etc n mainly devices which understand only json can use easily. Remember when we made Web Api over WCF or We service, we told now a refrigerator can talk to a remote APi
Link to video at 16:30 - th-cam.com/video/oDIkgNchrVY/w-d-xo.html
Thanks, this is a help in getting up the learning curve. Very good overview.
gRPC and REST are not mutually exclusive....
@gogators432 for small teams, using both I don't think that it's a good idea