4 ms·
i agree, was forced to use it at several companies and it was 99% not needed tech debt investment garbage even in go its a pain in the ass to have to regen and
by sitzkrieg 2y ago
i agree, was forced to use it at several companies and it was 99% not needed tech debt investment garbage
even in go its a pain in the ass to have to regen and figure out versioning shared protos and it only gets worse w each additional language
but every startup thinks they need 100 microservices and grpc so whatever
- hamandcheese 2y ago> even in go its a pain in the ass to have to regen and figure out versioning shared protos and it only gets worse w each additional language The secret is: don't worry about it. There is no need to regenerate your proto bindings for every change to the protos defs. Only do it when you need to access something new in your application (which only happens when you will be making changes to the application anyway). Don't try and automate it. That is, assuming you don't make breaking changes to your protos (or if you do, you do so under a differently named proto).