If you don't have a monorepo in your org, don't use gRPC. Specifically, if you can't maintain those .proto mess inside one single source of truth, you're proba

If you don't have a monorepo in your org, don't use gRPC. Specifically, if you can't maintain those .proto mess inside one single source of truth, you're probably fucked. If devs are afraid of updating .proto and adding many `context` or `extra` or `extension` fields, you are fucked. Get rid of gRPC ASAP! Look are your .proto definitions, if there are tons of <str,str> mapping or repeated key-value pairs, just forget gRPC, use JSON. Need performance? Use msgpack!