gRPC Conf 2019

This session will cover an in-depth overview of the Protolock CLI tool. I created Protolock after one-too-many accidental rollouts where our gRPC APIs had backward-incompatible changes. Maybe the new team member forgot about reserving names or changing identifiers, or a PR slipped through review with less attention than needed. Regardless, the Java team just @here'd our slack channel with a massive stack trace culminating with a null pointer exception... thanks to our API breaking their client. Protolock solves this problem with built-in rules checking for API incompatible changes (renaming fields, changing field types, changing streaming in/out of RPCs, etc) and can block builds or code-gen when changes are detected. It's plugin system allows developers to extend Protolock's functionality with their own rules, written in any language. Here's more about Protolock: https://docs.google.com/presentation/d/1QUGZ2VqTAIR-lF-dXI7b_vUjFA3C45bXpGhPWUX7AvI/edit#slide=id.p (note: old deck!)