4 ms·
I'm not sure I understand this. Isn't protobuf just one such protocol definition. With a focus on being general. If you don't like the trade-offs it makes the
by aleksiy123 3y ago
I'm not sure I understand this.
Isn't protobuf just one such protocol definition. With a focus on being general.
If you don't like the trade-offs it makes then you can use your own specific protocol with your own tradeoffs.
But yes people will push back on you if you can't justify why that decision is better than the general solution especially if they have to use it.
Imo starting with an out of the box solution as a baseline and then moving to a more specialized solution when the need arises is pretty solid decision.
- convolvatron 3y agoI think you answered my question. I’d like to say ‘what’s the most effective way to serialize this’ and everyone else wants to say ‘use protobuf unless you can come up with a really good reason not to’
- aleksiy123 3y agoYes makes sense. I think it's also about the context of what your goal is and what your eng skill set is. If you are low-level C shop that may make sense. But if you are trying to build some rpc service for usage between multiple teams and languages. Using protobufs or something similar is gonna give you more mileage.