krickert commented on PR #2916: URL: https://github.com/apache/tika/pull/2916#issuecomment-4859189416
@nddipiazza the biggest problem is that grpc is not compatible with rest and the other way around. They both work on different modeling concepts (I think the proto spec is 100x better). However, protos are easy to return as JSON but never the other way around. I'm gonna close this branch in favor of my new one. It comes down to this: you should always model your grpc service so it's grpc, not a mimic of REST. It's sorta like someone using hungarian notation in java code - it just looks strange. That being said, the app entities are not good at this. Everyone treats gRPC as second class and wants a shortcut, but that's the wrong approach. When you make the interface - you are coding 12 clients at the same time. It may look like a lot - but it's far less code. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
