Excuse me if this question seems a bit silly, but I'm wondering whether it
would
make sense to use FlightSQL to power a JSON API that talks to multiple
databases.

I know that the docs around Flight/FlightSQL say that there is a marked
performance improvement over ODBC/JDBC, but I assume this is only if the
service
sending the data over Flight isn't using one of these to interact with the
datasource, right?

If I have a JVM application using JDBC and sending the responses as JSON,
would
it still make sense to look towards implementing a FlightSQL Server because
of
the ability to distribute operations across multiple instances and it being
language-agnostic? Or would I be losing most of the benefits here?

Not familiar with the Arrow format and project as a whole, so still trying
to
wrap my head around things, sorry!

Thank you =)
Gavin Ray

Reply via email to