How is this different from grpc? #340
Replies: 1 comment
-
grpc is great for microservice communication but rspc is designed to be really good for communication between your frontend (Typescript, although more coming soon) and your backend (Rust). I haven't worked with grpc extensively but I think it's usally schema based. rspc infers your Rust types and uses it to generate the client from the frontend. This means you don't need to hardcode your return types and deal with complicated codegen on the backend. (It's possible Rust frameworks could generate the protobuf file but I haven't looked into it). rspc has a really typesafe middleware system, and many other features targetted at abstracting logic like authentication, rate-limiting, and more which you would want when building a frontend application but wouldn't matter for microservice communication. I would recommend trying both in a small-ish project and just go with whatever feels the most natural to you. |
Beta Was this translation helpful? Give feedback.
-
How is this different from grpc? Maybe with connect-es on the frontend?
Beta Was this translation helpful? Give feedback.
All reactions