grpc-migration-contract-distribution

To migrate gRPC proto modules to a contract distribution model, you split them into separate proto-only and generated code modules. This enables external consumers to compile protos using their own gRPC versions, avoiding transitive dependency conflicts.

Splitting proto definitions from generated gRPC code prevents transitive dependency conflicts. It allows external consumers to depend solely on proto contracts and compile against their own specific gRPC versions without inheriting unwanted library dependencies.

RFC-33 compliance in gRPC proto module distribution is achieved by separating proto definitions from generated code. This specific contract distribution model ensures external services integrate with a consistent, version-controlled contract without inheriting conflicting transitive gRPC dependencies.

Migrating gRPC proto modules does require a mandatory major version bump for the newly created proto-only module. This version increment is required alongside specific build.gradle modifications and directory restructuring to ensure proper contract distribution.

gRPC contract distribution requires specific directory structures that physically separate proto-only files from generated code modules. You must configure these paths within your build.gradle modifications to correctly split the monolithic proto definitions.