<@U078Y59KC3B> under what circumstances would I ne...
# ask-ai
s
@RunLLM under what circumstances would I need to use a Pulsar Proxy? What are the advantages and downsides of using this component over an existing load balancer like HAProxy?
r
You need to use a Pulsar Proxy when direct client connections to Pulsar brokers are infeasible or undesirable, such as in cloud or Kubernetes environments where brokers are not directly accessible. The Pulsar Proxy acts as a gateway, forwarding client requests to brokers, and supports features like TLS/mTLS, authentication, and seamless client failover without requiring client reconfiguration—clients just point to the proxy address. This is especially useful for multi-tenant, secure, or cloud-native deployments where network boundaries or security policies prevent direct broker access. According to Pulsar proxy docs and architecture overview, the proxy is optional but recommended in these scenarios. The main advantage of Pulsar Proxy over generic load balancers like HAProxy is its deep integration with Pulsar's protocol, service discovery, and security model. It understands Pulsar's binary protocol, supports broker lookups, and can forward authentication/authorization information. In contrast, HAProxy and similar L4/L7 load balancers do not natively support Pulsar's protocol and cannot perform Pulsar-specific routing or security functions. However, using a proxy adds another hop, potentially increasing latency, and requires additional configuration and resources. Also, Pulsar Proxy is not intended to be exposed directly to the public internet and relies on network perimeter security, whereas load balancers like HAProxy are designed for public exposure and broader protocol support. For SNI-based routing, external proxies like Apache Traffic Server (ATS) can be used, but not HAProxy or Nginx, as per SNI routing docs. Would you like more detail on specific deployment scenarios or configuration examples? Sources: - Pulsar proxy docs - Pulsar architecture overview - SNI routing docs 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.