News for hackers. Stuff that matters.
Re:Why We’re Switching to gRPC by gravypod on Tuesday May 28, 2019 @08:15AM (#20029280)
It would be done in CI. Generate stubs -> package/compile -> push to internal package repo.

This way your protocol for your infrastructure is just another library.

Re:Why We’re Switching to gRPC by q3k on Tuesday May 28, 2019 @09:33AM (#20029819)
Having an explicit 'create client library by generating/compiling proto stubs' is generally also bad mojo from my experience, unless you're also abstracting API stability and service discovery. If not, it will be unnecessarily painful to make a change to either the service discovery method or a non-backwards-compatible proto change, as you will have to lockstep both the service rollout, the library build and the client bump.