Re:Istio Observability with Go, gRPC, and Protocol Buffers-B...
by ec109685 on Sunday April 21, 2019 @12:05PM
(#19712697)
gRPC’s responses are backwards compatible, so you aren’t mandated to update all clients at the same time.
[ Parent
| on HN ]
Re:Istio Observability with Go, gRPC, and Protocol Buffers-B...
by lugg on Sunday April 21, 2019 @12:30PM
(#19712881)
You'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.
Re:Istio Observability with Go, gRPC, and Protocol Buffers-B...
by joshuamorton on Sunday April 21, 2019 @02:42PM
(#19713742)
I'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.
Re:Istio Observability with Go, gRPC, and Protocol Buffers-B...
by ehsankia on Sunday April 21, 2019 @03:03PM
(#19713864)
That'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.
Re:Istio Observability with Go, gRPC, and Protocol Buffers-B...
by nhooyr on Sunday April 21, 2019 @01:10PM
(#19713150)
JSON is as well.
Re:Istio Observability with Go, gRPC, and Protocol Buffers-B...
by isoskeles on Sunday April 21, 2019 @01:14PM
(#19713183)
JSON 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.