paul-rogers commented on issue #13469: URL: https://github.com/apache/druid/issues/13469#issuecomment-1381090285
@churromorales, thanks for your comments. You asked: > any reason why you wouldn't start with internal druid services talking to each other using grpc Changing Druid's internals is a touchy subject. Druid is very much committed to REST/JSON, despite any possible drawbacks. Further, there are many, many deployments and extensions that depend on the current RPC structure: changing Druid's RPC would be highly disruptive. We recognize that Protobuf has advantages: more efficient wire format, better versioning support, etc. We're just not convinced the advantages are worth the cost to upgrade. That is, there may be better uses for the effort that would go into any networking change. That said, a handy way to experiment is via an extension for a limited use case. That's what this little project does. In addition to solving a specific use case, it lets the project leadership get a bit of a taste of a non-JSON RPC. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
