Traditional reverse proxy servers and HTTP proxies are still commonplace in today’s network security stacks, but IT leaders increasingly cite issues with:
Latency: Proxies need to operate inline to intercept traffic. Routing traffic through bandwidth-limited appliances in a serial fashion can add significant latency to requests—particularly with on-site enterprise deployments—leading to a poor user experience.
Compatibility: Traditional proxies are prone to application compatibility issues because they weren’t built for the ways rich web-based applications perform authentication, API calls, service requests, and more, forcing additional troubleshooting.
Cost: Commercial proxy appliances cost too much compared to typical IT budgets—even more so if an organization wants to use them to inspect TLS/SSL traffic, for which some vendors can recommend as many as eight times more appliances.
Caching: Once a critical function of a proxy architecture, caching is now a feature of all modern web browsers, making network-based caching a secondary offering at best.
Read more.