On Thu, Jun 29, 2017 at 5:18 PM, Maurice Barnum <m...@yahoo-inc.com.invalid> wrote:
> this seems like it should be a solved problem.from a quick look, for > example, it seems like nginx can do this already. > https://www.nginx.com/resources/admin-guide/tcp-load-balancing/ > That would only work for the initial topic lookup. After that, the client discover that topic X is server on broker Y and it will try to directly connect to it. In the same way, when you connect the 2nd time, the proxy cannot just be a simple TCP proxy, because you need to specify which particular broker you want to connect to. So, I'm my proposal, this is done in the Connect/Connected phase, so the proxy knows which target it needs to connect to and after that it gets out of the way by doing simple buffer forwarding. -- Matteo Merli <matteo.me...@gmail.com>
