gRPC is a high-performance RPC protocol built on HTTP/2. We’re seeing more and more companies move their APIs from HTTP/JSON to gRPC. gRPC offers numerous benefits over HTTP/JSON:
* Performance. gRPC uses HTTP/2, with support for streaming, multiplexing, and more (see the difference in action). In addition, gRPC has native support for protobuf, which is much faster at serialization/deserialization than JSON.
* Streaming. Despite its name, gRPC also supports streaming, which opens up a much wider range of use cases.
* Code generation of endpoints. gRPC uses code generation from API definitions (.proto files) to stub out your endpoints.
gRPC does have a few downsides, the biggest of which is probably that it’s much newer than HTTP/REST, and, as such, the maturity of tools and libraries around gRPC isn’t anywhere close to HTTP. https://goo.gl/Rkcohf #DataIntegration #ML
