5 ms·
gRPC’s responses are backwards compatible, so you aren’t mandated to update all clients at the same time.
by ec109685 8y ago
gRPC’s responses are backwards compatible, so you aren’t mandated to update all clients at the same time.
- lugg 8y agoYou're still blocked from using later features potentially even reaching a dependency chain deadlock until you update. Systems like this work far better when you just work to not break backwards compatibility full stop. Similarly, they work better when you don't tangle up dependencies in a bunch of shared code, generated or otherwise.
- joshuamorton 8y agoI'm unclear what problem your describing. Your always blocked from using later features until an update because we'll, you won't have application code that can take advantage of those features until you update.
- ehsankia 8y agoThat's missing the point. Yes, the goal is to get to a state where all the services are running the new code, but the hard part is that transition. You can manually handle it using versioning and such, but gRPC handles that for you.
- nhooyr 8y agoJSON is as well.
- isoskeles 8y agoJSON is agnostic towards anything-compatibility. If you want your service to be backwards compatible, and it is serving JSON, I think you're only going to achieve your goal through rigorous 'integration' tests.