wjones127 opened a new issue, #34221: URL: https://github.com/apache/arrow/issues/34221
### Describe the enhancement requested For high-QPS (queries per second) servers, gRPC recommends implementing services using the Async APIs over the Sync API ([docs](https://grpc.io/docs/guides/performance/#c)). In some Flight designs, particularly ones where there is a single coordinator node that all clients go to before talking to the data nodes, the `ListFlights` and `GetFlightInfo` may see many queries per second. We should allow defining most endpoints using the callback gRPC API (completion queue is another option, but probably overly complex). We can probably keep methods that exchange Arrow data out-of-scope, since they are meant to be optimized for high-throughput rather than high QPS. I wonder if the signature of the methods could be something like: ```cpp Future<std::unique_ptr<FlightInfo>> GetFlightInfo(const ServerCallContext& context, const FlightDescriptor& request); ``` Though not sure if there is a straight-forward way to hook our `Future`s into the gRPC callback API. ### Component(s) C++, FlightRPC -- 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]
