Benchmarking gRPC+Protobuf vs HTTP+JSON in Go #golang
http://pliutau.com/benchmark-grpc-protobuf-vs-http-json/
Simplest possible solution for communication between services is to use JSON over HTTP. Though JSON has many obvious advantages - it’s human readable, well understood, and typically performs well - it also has its issues. In the case of internal services the structured formats, such as Google’s Protocol Buffers, are a better choice than JSON for encoding data. gRPC uses protobuf by default, and it’s faster because it’s binary and it’s type-safe.
http://pliutau.com/benchmark-grpc-protobuf-vs-http-json/
Simplest possible solution for communication between services is to use JSON over HTTP. Though JSON has many obvious advantages - it’s human readable, well understood, and typically performs well - it also has its issues. In the case of internal services the structured formats, such as Google’s Protocol Buffers, are a better choice than JSON for encoding data. gRPC uses protobuf by default, and it’s faster because it’s binary and it’s type-safe.