The best rpc frameworks, according to hackers
5 rpc frameworks recommended in Hacker News comments over the past year, ranked by how many separate people recommend each one.
All rpc frameworks
- gRPCRecommended for typed service interfaces, generated clients and strong backend use across many languages; critics say it is heavy and poorly suited to browsers and plain HTTP.25recommend
- ConnectRPCDevelopers recommend it as a gRPC-compatible HTTP API framework that works with Protobuf and generates typed clients. One critic notes few languages have server support.15recommend
- tRPCRecommended for end-to-end type safety by sharing TypeScript types between frontend and backend. Main caveat: no spec or schema, so it relies on the type system and ties you to its RPC system.12recommend
- Apache ThriftPraised for cleanly abstracting data formats and transports, and for handling very large loads at Twitter; the most common caveat is poor documentation.8recommend
- VarlinkA JSON-based IPC protocol from the systemd world, a simpler D-Bus alternative without a broker. Critics note it lacks many-to-many communication.7recommend