Apache Traffic Server vs frp

Apache Traffic Server is a free, open-source caching proxy server for HTTP/1.1 and HTTP/2. It stores frequently requested pages, images, and web service calls so they can be reused, with the stated aims of improving response time and reducing server load and bandwidth needs. It can also add keep-alive behavior, filter or anonymize requests, and balance traffic through a proxy layer. Deployment patterns include web proxy cache, reverse proxy, and cache hierarchy. As a layer 7 HTTP load balancer, it can choose next-hop servers using request attributes, weighted round robin, or URL consistent hashing. Plug-in APIs let teams add behavior such as changing headers, handling ESI requests, or implementing cache algorithms. Security options include client access controls and authentication, SSL termination, and SSL-based access control. It is self-hosted, with Linux and macOS listed as platforms. The project identifies enterprises, internet service providers, backbone providers, and large intranets as its intended audience. The listed stable release is 10.2.0; 9.2.15 is listed as the long-term support release.

frp is a free, self-hosted reverse proxy for making intranet services reachable from the public network through nodes with public IP addresses. It supports TCP, UDP, HTTP, and HTTPS proxying, while client-server communication also supports QUIC, KCP, WebSocket, and other protocols. Its XTCP mode uses P2P hole punching so successful connections send traffic directly rather than through frps, but success depends on the network’s NAT type and cannot be assured. Client and server authentication support tokens and OIDC, with token authentication as the default; encryption is among the project’s listed capabilities. Proxy groups can balance load, and TCP or HTTP health checks can remove failed services from frps. Monitoring can run in memory or through Prometheus, which requires the Dashboard to be enabled. frps has a browser Dashboard for status and proxy statistics, while frpc includes an Admin UI for proxy status and configuration. Configuration supports TOML, YAML, and JSON; INI is still supported but no longer recommended. Written in Go, frp provides platform-specific binaries for cross-platform deployment without additional dependencies. The project is under development and says version 2 will not be compatible with version 1.