News for hackers. Stuff that matters.

A comment on Demystifying the protobuf wire format. Parent comment

Re:Demystifying the protobuf wire format by beeboobaa3 on Friday May 17, 2024 @10:46AM (#40390525)
But... Why? How is envoy, a proxy, related to your choice to use protobuf? How are your gripes with envoy relevant? This just smells like bad design
[ Parent | on HN ]
Re:Demystifying the protobuf wire format by bairen on Friday May 17, 2024 @12:33PM (#40391653)
Yes, using envoy was bad design in our situation. It was premature optimisation.

We could either maintain a grpc API and a rest API , or a grpc API plus envoy, or 1 rest API.

I am saying we should have picked 1 rest API and only switched to grpc if and when we ran into scaling problems.

Avoiding having to maintain grpc compilers and envoy in our security updates.

[ Parent | on HN ]
Re:Demystifying the protobuf wire format by aaomidi on Friday May 17, 2024 @05:37PM (#40394426)
Grpc isn’t just for scaling though. It’s a schema format that comes with code generation you can technically avoid the code generation if you so please.

Idk I think people are expecting either too much or too little of these tools.

[ Parent | on HN ]