All 15 gRPC Services questions
More in gRPC Services
How do you implement a gRPC server method in ASP.NET Core, and how does it integrate with the standard hosting model? What is gRPC-Web, and why is it needed for calling gRPC services directly from a browser-based JavaScript client? How do you implement server-streaming gRPC using C#'s IAsyncEnumerable<T> or IServerStreamWriter<T>? What is protobuf field numbering, and why must you never reuse or renumber a field once a message definition has shipped to production? How does client-side load balancing work for gRPC when calling a service with multiple backend instances, without a dedicated load balancer? What are the four types of gRPC service methods (unary, server streaming, client streaming, bidirectional streaming), and when is each appropriate? How does gRPC handle errors and status codes, and how does this differ from HTTP status codes in REST? How does gRPC's use of HTTP/2 multiplexing provide performance advantages over HTTP/1.1-based REST APIs? How does gRPC support interceptors for cross-cutting concerns like authentication, logging, and retries, similar to middleware in a REST pipeline? How do you handle authentication for gRPC calls, and how does it differ from typical REST API authentication patterns?
Advertisement
Back to results for “gRPC Services”
.NET › gRPC Services

How would you version a gRPC service's contract while maintaining backward compatibility with existing clients?

Intermediate

Answer

Protobuf inherently supports additive, backward-compatible evolution: adding new fields (with new numbers) to existing messages doesn't break old clients (which simply ignore unknown fields) or old servers (which see new fields as absent/default on requests from newer clients) -- for genuinely breaking changes (removing or fundamentally changing a field's meaning), the convention is defining an entirely new service or method (like GetOrderV2) or a new package/namespace, similar in spirit to REST's URL-based versioning but expressed through the protobuf package/service naming instead.
// Adding a field is safe -- old clients simply don't send/see it
message OrderRequest {
  int32 order_id = 1;
  string include_details = 2;  // NEW field, old clients omit it, defaults apply
}

// Breaking change: new service version entirely
service OrderServiceV2 {
  rpc GetOrder (GetOrderRequestV2) returns (OrderResponseV2);
}
Real-world example An internal platform evolves its OrderService contract by only ever adding new optional fields for two years, avoiding the need for a breaking V2 service entirely, since protobuf's additive-evolution model accommodated every required change without compatibility issues.

Common follow-ups: How does protobuf handle a field present in a newer message but absent in the client's older generated code?;When is a new service version truly unavoidable versus additive evolution being sufficient?

API Versioning;Microservices & Distributed Architecture Patterns
All 15 gRPC Services questions