Comment on Demystifying the protobuf wire formatparentComments−bairen2yYes, 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.−aaomidi2yGrpc 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.
Comments
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.
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.