golang-grpc

Structure protobuf files using domain and versioned directories with Request/Response wrapper messages. This layout allows gRPC APIs to evolve safely without breaking existing clients when new fields or message types are introduced.

Handle gRPC errors by returning grpc status.Error with appropriate codes. Mapping domain errors to standard gRPC status codes ensures clients receive structured, actionable failure information instead of opaque or undefined responses.

Test gRPC services using the bufconn package to create an in-memory listener. This approach allows you to dial the server without binding to a real network port, making unit tests faster and more isolated.

Implement graceful shutdown by calling GracefulStop on the gRPC server with a timeout fallback. This ensures in-flight RPCs complete or the server forces a shutdown after a specified duration, preventing hung connections.

Yes, the gRPC Skill guidance supports configuring TLS and mTLS for Go services. It provides production security guidance including mutual TLS setup and recommends disabling server reflection in secure environments.

gRPC clients experience connection exhaustion when connections are not reused properly. Ensure client connection reuse, implement per-RPC deadlines, and configure metadata propagation to maintain client reliability under high load.