grpc-integration-patterns

gRPC enables high-performance inter-service communication in ABP by using Protobuf contracts and HTTP/2 transport. Define service contracts in .proto files, generate code, then implement gRPC services within ABP's dependency injection and multi-tenancy layers alongside REST endpoints.

Yes. gRPC services in ABP integrate with built-in multi-tenant filtering and error handling. The Skill shows how to consume gRPC clients in AppServices while preserving ABP's tenant isolation and context propagation across streaming and unary RPCs.

gRPC supports four streaming patterns: unary RPC for single request-response, server streaming for sending multiple responses, client streaming for receiving multiple requests, and bidirectional streaming for simultaneous two-way communication—enabling bulk data transfer and real-time event flows.

Use gRPC client streaming to ingest bulk data in batches. Client streaming accepts multiple requests in a single connection, significantly improving throughput and reliability over REST for high-volume license plate data, sensor readings, or batch operations.

Protobuf is central to gRPC's approach. The Skill covers Protobuf-first development—defining service contracts in .proto files as a single source of truth—with code generation handling client and server stubs so you work in C# while maintaining strongly-typed contracts.

gRPC uses HTTP/2 and binary Protobuf for lower latency, streaming support, and efficient bandwidth use compared to REST's text-based JSON over HTTP/1.1. gRPC suits high-performance internal APIs; REST remains simpler for public-facing services.