Interoperability

Fory gRPC peers interoperate only when they use the same generated service contract, matching Fory type identities, and compatible generated model schemas.

Protocol boundary

The transport is gRPC, but the message bytes are Fory payloads. Generic protobuf clients and server reflection tools cannot decode those payloads as protobuf messages. Generate every peer through a supported Fory compiler frontend.

Supported generated companions

Java, Python, C++, Go, Rust, JavaScript/TypeScript, C#, Dart, Scala, and Kotlin have documented gRPC companions. Use the support matrix and the selected runtime page for current dependencies and streaming support.

Verification

Test at least one unary call and every streaming shape used by the service. A protobuf UNIMPLEMENTED or decode failure usually means the peer used an ordinary protobuf stub or a different generated service contract.