[
https://issues.apache.org/jira/browse/HBASE-17721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893129#comment-15893129
]
stack commented on HBASE-17721:
-------------------------------
grpc or go home I'd say (unless perf is abysmal -- haven't tried). Would be
sweet if our web port could be taught to do grpc so we didn't have to put up
another port (https://groups.google.com/forum/#!topic/grpc-io/JnjCYGPMUms
https://github.com/grpc/grpc/issues/8043). This one is related too I'd say:
HBASE-8691 (love this issue).
> Provide streaming APIs with SSL/TLS
> -----------------------------------
>
> Key: HBASE-17721
> URL: https://issues.apache.org/jira/browse/HBASE-17721
> Project: HBase
> Issue Type: Umbrella
> Reporter: Alex Araujo
> Assignee: Alex Araujo
> Fix For: 2.0.0
>
>
> Umbrella to add optional client/server streaming capabilities to HBase.
> This would allow bandwidth to be used more efficiently for certain
> operations, and allow clients to use SSL/TLS for authentication and
> encryption.
> Desired client/server scaffolding:
> - HTTP/2 support
> - Protocol negotiation (blocking vs streaming, auth, encryption, etc.)
> - TLS/SSL support
> - Streaming RPC support
> Possibilities (and their tradeoffs):
> - gRPC: Some initial work and discussion on HBASE-13467 (Prototype using GRPC
> as IPC mechanism)
> -- Has most or all of the desired scaffolding
> -- Adds additional g* dependencies. Compat story for g* dependencies not
> always ideal
> - Custom HTTP/2 based client/server APIs
> -- More control over compat story
> -- Non-trivial to build scaffolding; might reinvent wheels along the way
> - Others?
> Related Jiras that might be rolled in as sub-tasks (or closed/replaced with
> new ones):
> HBASE-17708 (Expose config to set two-way auth over TLS in HttpServer and add
> a test)
> HBASE-8691 (High-Throughput Streaming Scan API)
> HBASE-14899 (Create custom Streaming ReplicationEndpoint)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
