3 ms·
As I understand, protobuf has compatibility (it stores field ids), so new service can read request from older client, and vice versa, so you do not need to refa
by codedokode 6mo ago
As I understand, protobuf has compatibility (it stores field ids), so new service can read request from older client, and vice versa, so you do not need to refactor anything. Also, it is made for long-range communications, and is inefficient for inter-process or inter-thread messaging.
- sa46 6mo agoPresumably, OP refers to the generated rust types which depend on the specific protobuf framework. I had the same issue when looking to adopt ConnectRPC for Go, which uses a custom wrapper type to model requests.