Hi all, What are the 'best practices' for handling service changes and API versioning in gRPC? At the protobuf level, I know the answer is: append fields and never reuse a field number. Or at the very least, comment out the field and wait until you can be sure that no component uses the old field.
But there are two scenarios that I can think of: - Adding RPC methods or altering RPC method signatures. I assume both the client and the server need to agree here? Do people implement a "GetVersion()" method? or something else? - When the client wants to send fields in a request that are semantically required but the server's version of the protobuf doesn't include those fields. Is there a way for the server to indicate that it received fields that it could not parse? Thank you! ~ Scott -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAJrQjStWaNNC3D0T%3DWSz-5p4Dh0s968m4%3DX%3DX1vdx0YVnRhkWA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
