Apache Traffic Server

Apache Traffic Server is a fast, scalable, and battle-tested HTTP caching proxy used by some of the largest content networks in the world. This appliance runs it as a reverse proxy and origin shield: point it at your backend origin and Traffic Server caches and serves responses close to your users, absorbing load and shortening the delivery path.

Key features

• High-performance HTTP/HTTPS caching reverse proxy and origin shield
• Reduce origin load and egress by serving cacheable responses from the edge
• Keep-alive connection reuse and request coalescing to your backend
• Runs the official, unmodified trafficserver/trafficserver container
• Ships with a built-in landing page so the proxy answers HTTP 200 before you wire up an origin
• Simple seeded configuration: one upstream origin and one listen port, no web console to manage

Use cases

• Put a caching origin shield in front of a web app, API, or media origin
• Offload and accelerate a slow or distant backend from a PoP near your users
• Add a regional cache tier in front of object storage or a packager

Why run it on the NetActuate edge Running Traffic Server in a PoP near your audience serves cacheable content locally, cuts round-trips and egress back to your origin, and keeps a caching tier on infrastructure you control.

Deployed from the NetActuate marketplace, Traffic Server boots pre-configured from your seeded values: set the origin host to cache and shield and the reverse-proxy port to listen on. There is no login to configure; the proxy answers on the instance IP as soon as the instance is up. Leave the origin blank and the appliance serves a co-located instructions page so you can confirm it is running, then point it at your backend.