4 ms·
This might be a dumb question, but why translate REST to gRPC and not expose the gRPC services directly?
by DandyDev 8y ago
This might be a dumb question, but why translate REST to gRPC and not expose the gRPC services directly?
- buckhx 8y agoBrowsers don't speak grpc natively. There is a separate spec for browser support, but it's a very new project https://github.com/grpc/grpc-web/blob/master/README.md https://github.com/grpc/grpc-web/blob/master/README.md
- nzoschke 8y agoOP here. We considered this, but decided against it for a couple reasons. First and foremost our customers universally favor REST APIs. GraphQL and gRPC are better tech wise but REST is more familiar. Next gRPC uses pure HTTP/2 which doesn’t work with an AWS ALB. Thanks to the grpc ecosystem the HTTP/1 and REST transcoding is just an Envoy config.