[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238127#comment-14238127
]
Jan Fernando commented on PHOENIX-971:
--------------------------------------
[~lhofhansl] From the app developers viewpoint, beyond client side jar
management, the big appeal of having a "thin" client with more typical RDBMS
JDBC driver resource utilization characteristics is that it much easier to work
with and scale out in a typical heterogenous, resource constrained app server
environment. Of course, that has to be traded-off against additional
operational complexity and hardware requirements for another service. But if
the kinds of operations we need the client to do require a lot more compute
power than a traditional RDBMS JDBC driver it can make it challenging to run
amongst a set heterogenous app server activity, particularly, when capacity
planning assumes close to a 1:1 ratio of HTTP requests to threads.
> Query server
> ------------
>
> Key: PHOENIX-971
> URL: https://issues.apache.org/jira/browse/PHOENIX-971
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Andrew Purtell
>
> Host the JDBC driver in a query server process that can be deployed as a
> middle tier between lighter weight clients and Phoenix+HBase. This would
> serve a similar optional role in Phoenix deployments as the
> [HiveServer2|https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2]
> does in Hive deploys.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
