gRPC integration
Use a generated client whose service definitions match the server release. gRPC is an optional integration path; most applications can start with a language client or the HTTP API.
Connection settings
Section titled “Connection settings”gRPC is served on the database port (--http-addr, default 7173) by default; --grpc-addr with another port adds a dedicated gRPC listener. Provide matching TLS and authentication settings in the client; see connection addresses and TLS and authentication.
Validate the contract
Section titled “Validate the contract”Check service and method names, parameter types, response schemas, error mapping and streaming behavior against the published definitions for your release. Generate code from those definitions rather than manually implementing a transport.
Application behavior
Section titled “Application behavior”Set deadlines and handle cancellation and connection errors. A failed response can leave the outcome of a write uncertain; reconcile using stable application identifiers before retrying.
Configuration · Troubleshooting
Related
Section titled “Related”This site uses Google Analytics cookies to count visits. Privacy · License