Fory gRPC
Fory gRPC combines normal gRPC transport semantics with request and response models generated by the Fory compiler. The payload marshaller uses Fory rather than protobuf message bytes.
When to Use It
Use Fory gRPC when every peer is generated from the same Fory IDL, protobuf IDL, or FlatBuffers IDL contract and supports the matching Fory runtime. Use ordinary protobuf gRPC when generic protobuf clients, reflection tools, or protobuf message bytes are required.
Schema Frontends
Fory gRPC companions can be generated from:
The compiler's Generated Code reference describes the model and service artifacts. Use Build Integration to wire generation into a project build.
Workflow
- Define messages and services in a supported compiler frontend.
- Generate models and gRPC companions with
foryc. - Add the normal gRPC dependencies for the selected runtime.
- Implement the generated server base and call the generated client.
- Verify unary and streaming calls between generated peers.
Python generates asynchronous grpc.aio companions by default and supports sync
generation with --grpc-python-mode=sync. JavaScript uses @grpc/grpc-js for
Node.js; browser clients are generated separately with --grpc-web and use
grpc-web.
Runtime Guides
| Runtime | Guide |
|---|---|
| Java | Java |
| Python | Python |
| C++ | C++ |
| Go | Go |
| Rust | Rust |
| JavaScript/TypeScript | Node.js and gRPC-Web |
| C# | C# |
| Dart | Dart |
| Scala | Scala |
| Kotlin | Kotlin |
See Architecture for payload and transport ownership and Interoperability for peer compatibility.