On Fri, Jun 30, 2017 at 5:09 PM, Dave Fisher <dave2w...@comcast.net> wrote:
> One thought is make the proxy into a WebSocket frontend but then pass > through to the broker using the TCP protocol. > > WebSocket would fit a pattern that everyone is used to scaling. It could > be setup through Tomcat with connections through a VIP. > The problem is still related to the stateful nature of the brokers (a topic is only served at a particular point in time), so the VIP cannot just route to any random broker. So, even if we change the client to always connect through the WebSocket service, it would still need some way to indicate which broker it needs to connect to. Side note: Pulsar already provides a WebSocket service, and that is used to expose an "easier" interface that you can use from whatever language. The problem is that it's not meant to be super-performant (the exchanges between client and server happen in JSON and the payloads are serialized in base64.. Matteo -- Matteo Merli <matteo.me...@gmail.com>
