gRPC, a high-performance RPC framework, has revolutionized API deployment for Google employees. Despite its efficient contract-focused structure and wide language support, gRPC has downsides, such as complex unary RPC implementation and mandatory code generation. Compatibility issues with HTTP/2 and late adoption of HTTP/3 have also posed challenges. The lack of standardized JSON mapping initially hindered accessibility for JSON-oriented developers. Additionally, protobuf’s limitations with finite message sizes can complicate handling large files. However, improvements such as HTTP/3 support and tools like Buf CLI and ConnectRPC are addressing these issues. Acknowledging and addressing these challenges will help unlock gRPC’s full potential for developers.
https://kmcd.dev/posts/grpc-the-bad-parts/