Whats the impact on the corporate firewall/proxy infrastructure when Kaazing Enterprise Gateway is employed?
If a customer has 100,000 or greater socket connections open thru the firewall/proxy, how much of a burden does this put on the FW/PX infrastructure? Firewalls (unlike proxies) typically work at the IP layer, not the TCP layer, so the scalability of the firewall is largely unaffected by the specific usage of IP traffic. In other words, firewalls are mostly about the number of IP packets per second and don’t particularly care whether those IP packets are shared by a small or large number of TCP connections because that IP-usage information is opaque to the firewall. Even when the TCP port number becomes relevant to the firewall for finer-grained access policies, the scalability of the firewall still comes down to the number of IP packets per second. Proxies, whether they be SOCKS or HTTP proxies, are typically used to holding on to lots of concurrent TCP connections, across many different end-users in the organization. By its very nature, SOCKS proxies must bridge individual TCP connect
Related Questions
- Is my network infrastructure taxed more heavily when I deploy Kaazing Enterprise Gateway as opposed to Comet and AJAX?
- Whats the impact on the corporate firewall/proxy infrastructure when Kaazing Enterprise Gateway is employed?
- Whats the impact on the corporate firewall/proxy infrastructure when Kaazing WebSocket Gateway is employed?
