grpc

Implement server-side streaming by defining an RPC that returns a stream in your proto file, then yielding responses from a generator in your servicer method. Each yield sends one message to the client, letting you throttle or break the stream as needed.

Set errors on the servicer context using context.set_code with a StatusCode like NOT_FOUND, plus context.set_details for a human-readable message. Return an empty response message afterward so the client receives the proper status instead of a generic failure.

Use gRPC for high-performance service-to-service communication, streaming workloads, and strongly typed contracts via protobuf. Prefer REST for simple CRUD APIs, browser-facing endpoints, or when human-readable payloads and broad tooling support matter more.

Configure deadlines and timeouts on calls, enable compression for large payloads, set keepalive pings, use connection pooling on clients, and add interceptors for auth and logging. Disable server reflection in production to avoid exposing your service schema.

Explicit field numbers define the binary wire format and must stay stable for backward compatibility. Changing or reusing a number breaks deserialization for existing clients, so numbers are assigned once starting from 1 and never recycled.