3 ms·
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,
by bairen 2y ago
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.
- aaomidi 2y agoGrpc 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.