A drop-in, lightweight gRPC replacement.

• DRPC website
• Examples
• Quickstart documentation
• Launch blog post

• Simple, at just a few thousand lines of code.
• Small dependencies. Only 3 requirements in go.mod, and 9 lines of go mod graph!
• Compatible. Works for many gRPC use-cases as-is!
• Fast. DRPC has a lightning quick wire format.
• Extensible. DRPC is transport agnostic, supports middleware, and is designed around interfaces.
• Battle Tested. Already used in production for years across tens of thousands of servers.

• go.bryk.io/pkg/net/drpc

  • Simplified TLS setup (for client and server)
  • Server middleware, including basic components for logging, token-based auth, rate limit, panic recovery, etc
  • Client middleware, including basic components for logging, custom metadata, panic recovery, etc
  • Bi-directional streaming support over upgraded HTTP(S) connections using WebSockets
  • Concurrent RPCs via connection pool

• Open an issue or join the Zulip chat if you'd like to be featured here.

DRPC can be made compatible with RPC clients generated from other languages. For example, Twirp clients and grpc-web clients can be used against the drpchttp package.

Native implementations can have some advantages, and so some bindings for other languages are in progress, all in various states of completeness. Join the Zulip chat if you want more information or to help out with any!

DRPC is licensed under the MIT/expat license. See the LICENSE file for more.

These microbenchmarks attempt to provide a comparison and come with some caveats. First, it does not send data over a network connection which is expected to be the bottleneck almost all of the time. Second, no attempt was made to do the benchmarks in a controlled environment (CPU scaling disabled, noiseless, etc.). Third, no tuning was done to ensure they're both performing optimally, so there is an inherent advantage for DRPC because the author is familiar with how it works.