The team and I are happy to answer any questions you might have about fRPC, Frisbee, or Loophole in general!
We wrote fRPC because we really liked the DevX and tooling around the proto3 syntax, but we needed the generated code to be significantly more performant than what gRPC provides.
We also needed the ability to extend the RPC framework with other messaging patterns (like pub/sub) and we needed to be able to reuse the underlying TCP connections as required.
Today, fRPC can outperform gRPC by more than 4x, doing more than 2 million RPCs/second on a single node.
Founder of Loophole Labs here!
The team and I are happy to answer any questions you might have about fRPC, Frisbee, or Loophole in general!
We wrote fRPC because we really liked the DevX and tooling around the proto3 syntax, but we needed the generated code to be significantly more performant than what gRPC provides.
We also needed the ability to extend the RPC framework with other messaging patterns (like pub/sub) and we needed to be able to reuse the underlying TCP connections as required.
Today, fRPC can outperform gRPC by more than 4x, doing more than 2 million RPCs/second on a single node.
You can check out our docs site at https://frpc.io, or check out the repo at https://github.com/loopholelabs/frpc-go