grpc

gRPC enables fast, reliable inter-service communication using proto-first contracts. Define your proto services in Protos/, implement server and client patterns in GrpcServices/, register them in Program.cs, and enable reflection in development for debugging and service discovery across validator, peer, and wallet modules.

Streaming RPC patterns in gRPC support scalable, resilient peer communication where data flows continuously rather than in single request-response cycles. Use server streaming for pushing updates, client streaming for batch operations, and bidirectional streaming for workflows requiring real-time two-way communication between services.

Yes. gRPC integrates with .NET and Protocol Buffers to define strong-typed service contracts. Proto files specify service definitions and message schemas, which compile to .NET types, enabling type-safe client and server implementations across Sorcha's service modules.

Enable gRPC reflection in development to inspect service definitions and test RPC methods without source access. Configure dual-port setup—one for standard gRPC traffic, one for reflection—and use reflection-enabled tools to explore available services and troubleshoot inter-service communication.

gRPC error handling uses status codes and messages to communicate failures across service boundaries. Implement retry logic, timeout policies, and proper status code propagation in both client and server to ensure resilient peer communication and graceful degradation in distributed workflows.