Software Development

Public gRPC API Design

Design a public gRPC surface for external developers - the when-gRPC-at-all gate (most platforms keep gRPC internal and publish REST or transcoded JSON), AIP proto package and versioning conventions, buf breaking-change gates and their google.api.http blind spot, unary-by-default streaming decisions, the google.rpc.Status error model with its HTTP-mapping traps, transcoding and gateway architecture (Connect-RPC, grpc-gateway, Envoy), and external auth and TLS. Use whenever the user mentions gRPC, protobuf or .proto files, buf, Connect-RPC, grpc-gateway, or gRPC-JSON transcoding at a public edge - even if they never say "gRPC API design". Design layer only, not language-specific server implementation.

Publisher / source
samber/developer-platform-skills (found on skills.sh)
Upstream record
samber/developer-platform-skills
Version
Version 3
Published
Publication review
Approved for publication
Content fingerprint
ce2048d90824acda5e4de910564e915a66e7356dc6c56a30b59b33f2e3583e81