Whole Clusters run on grpc like k8s + istio and it's well supported by proxies like envoy.
You could think about clients talking to their user's topics directly, authenticated by ingress - e.g. envoy filters (see https://www.envoyproxy.io/docs/envoy/latest/configuration/http_filters/grpc_web_filter for ideas). IMHO, I'm not convinced about GCP pub-sub. Making one thing like the other is almost often a large effort and a bad fit if you look into details. When google changes the api, do you follow? Wrapping your already proofen, tested and implemented custom protocol in grpc is probably a huge time saver. And your clients apis are well-designed like they are. Better early than google like ;) [ Full content available at: https://github.com/apache/incubator-pulsar/issues/271 ] This message was relayed via gitbox.apache.org for [email protected]
