ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #grpc
Context A gRPC service mesh spans Java, Go, and Python services. The team must choose a single load balancing policy for all clients to simplify operations. Constraint The gRPC specification defines pick_first and round_robin policies but does not mandate NameResolver re-resolution intervals. Java's DnsNameResolver uses a fixed refresh interval, while Go's r
Goal: Keep the gRPC client connection pool from exhausting file descriptors or memory by preventing dead connections from lingering, while keeping keepalive‑induced overhead low enough to stay within middlebox idle‑timeout limits and avoid unnecessary CPU/network load. Constraint: The exact idle timeout enforced by firewalls, sidecar proxies or cloud load ba
When a gRPC client sets a deadline, the remaining time is encoded in the grpc-timeout header and enforced across the RPC lifecycle. In a multi-hop service graph, the framework does not automatically chain that budget through independent downstream stubs, leaving teams to decide whether to propagate the original deadline or reserve a fresh budget per hop. Reu
The goal is to keep a local developer setup repeatable so that a gRPC Java client always connects to the same backend instance during debugging and testing. Starting with version 1.44.0 the library changed the channel‑level default from pick_first to round_robin unless an explicit policy is supplied. This alters the connection‑establishment pattern seen agai
An application deploys a new gRPC service version that adds optional fields to existing protobuf messages. The older binary, still running in production, must continue to parse messages produced under the newer schema. If the service is rolled back to the previous binary, does the older version reliably interpret the additional fields without data loss or mi
When using Google Cloud client libraries, developers typically implement timeouts or cancellation tokens to prevent application hangs. While these mechanisms ensure the client receives a DeadlineExceeded or Canceled status, the behavior of the backend service varies depending on the transport layer (gRPC vs. REST) and the specific API implementation. For sta
The goal is to determine whether a browser-based gRPC-Web client can call a standard gRPC service directly over HTTP/2, or whether a translation proxy is mandatory at the integration boundary. gRPC-Web uses distinct message framing and content encoding compared with canonical gRPC-over-HTTP/2. Native gRPC-Web acceptance, where offered by a server framework,
Goal: align tablet certificate SANs with the address Vitess clients use for gRPC TLS connections in a Kubernetes deployment. Vitess components encrypt inter-component gRPC traffic with TLS, and Go gRPC clients verify the hostname by default. If VTGate addresses a tablet using a Kubernetes headless service DNS name while the tablet certificate contains only t
When using the gRPC Java Netty transport, long‑running services occasionally observe that idle connections are closed after a short period of inactivity, even though no explicit idle timeout has been configured. The library selects a platform‑dependent default value for the Netty idle‑timeout handler, and the exact number is not documented in the API referen
vitess
kubernetes
java