It mostly works, but it's a kludge to overcome the fact that grpc isn't designed for the web to begin with, where Graphql is a much better choice for web apps.įor mobile apps, the situation is a bit different. (You can see an explanation of all this here: ). Essentially, browsers can't implement the grpc spec, so you need to use a related technology called grpc-web, which relies on a proxy in the backend that translates calls from grpc-web to grpc. I used grpc in a web project a few years ago, and based on my experience I wouldn't do it again. Graphql does have support for subscriptions but I am not sure how good it scales with respect to thousands of users as grpc has support for load balancing and all other stuff by default.Ĭan anyone list pros and cons of graphql with respect to Grpc. Our app will have real time communication as well which grpc has very great support. Some of the grpc sample on grpc.io are difficult to get you head around for android, iOS swift has completely different repo maintained on GitHub and same for web as well.Īlso most of the comparisons I see on graphql is with respect to rest apis. From frontend perspective I see more love to graphql than grpc. We are gonna use the backend service for mobile and web. Graphql is more widely used in js community as compared to others. One of our senior engineer is saying to use grpc as it is framework agnostic and easy to implement micro services architecture in different language. Our company is trying to choose between graphql and grpc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |