How do I install Apache Traffic Server on Ubuntu?

Install dependencies like libssl-dev and libpcre2-dev, then use cmake to build from source as outlined in the README's Ubuntu/Debian section. For production, consider using pre-built packages or the contrib scripts for automation.

Apache Traffic Server vs Nginx: which is better for caching?

ATS is optimized for high-scale caching with deep plugin extensibility and native HTTP/3 support, while Nginx offers easier configuration and broader web server features. Choose ATS for large CDNs or custom edge computing, and Nginx for general-purpose proxying with simpler setup.

What plugins are available for Apache Traffic Server?

ATS includes core plugins for caching, logging, and more, with experimental options in the plugins directory. You can also develop custom plugins using the C/C++ API, but community-contributed plugins are less abundant than for some alternatives.

Does Apache Traffic Server support HTTP/3?

Yes, it implements HTTP/3 with QUIC for improved connection efficiency, as mentioned in the key features and source code under src/iocore/net/quic. Ensure your build includes the necessary dependencies and configuration.

How to configure caching rules in ATS?

Use configuration files in /etc/trafficserver, such as cache.config, to define caching policies based on URL patterns or headers. The admin guide on the wiki provides detailed examples, but it requires manual tuning for optimal performance.

Can I use ATS as a reverse proxy for microservices?

Yes, it functions as a reverse proxy with load balancing and caching capabilities. Configure remap.config for routing, and leverage plugins for advanced features, but be prepared for complex setup compared to lighter proxies like Envoy.

Open-Awesome

Traffic Server

Apache-2.0C++

A fast, scalable, and extensible HTTP/1.1, HTTP/2, and HTTP/3 compliant caching proxy server for building cloud services.

Visit Website GitHub

2.0k stars863 forks0 contributors

What is Traffic Server?

Apache Traffic Server is a high-performance, scalable caching proxy server that supports HTTP/1.1, HTTP/2, and HTTP/3. It accelerates web traffic by caching content, reducing latency, and decreasing load on origin servers, while also serving as an extensible platform for building large-scale cloud services through its plugin architecture.

Target Audience

System administrators, DevOps engineers, and developers building or managing high-traffic web infrastructure, content delivery networks (CDNs), and cloud services requiring robust caching and proxy capabilities.

Value Proposition

Developers choose Apache Traffic Server for its proven performance at scale, extensive plugin ecosystem, and comprehensive support for modern HTTP protocols, offering a flexible and open-source alternative to commercial caching and proxy solutions.

Overview

Apache Traffic Server™ is a fast, scalable and extensible HTTP/1.1 and HTTP/2 compliant caching proxy server.

Use Cases

Best For

Accelerating static and dynamic content delivery for high-traffic websites
Building custom CDN or edge computing platforms
Implementing reverse proxy and load balancing for microservices architectures
Reducing origin server load through intelligent caching strategies
Extending proxy functionality with custom plugins for specific use cases
Improving web performance with HTTP/2 and HTTP/3 protocol support

Not Ideal For

Small-scale websites or personal blogs with minimal traffic where caching overhead isn't justified
Teams lacking dedicated DevOps or system administration expertise for complex configuration and tuning
Use cases requiring out-of-the-box web application features like built-in authentication or WAF without custom plugins
Environments where quick deployment with minimal learning curve is prioritized over ultimate performance

Pros & Cons

Pros

High-Performance Caching

Supports HTTP/1.1, HTTP/2, and HTTP/3 with QUIC for fast proxy caching, reducing latency and origin server load as highlighted in the key features.

Extensible Plugin Architecture

Includes stable and experimental plugins, allowing customization for large-scale applications, evidenced by the plugins directory in the README's structure.

Modern Protocol Support

Implements HTTP/3 and QUIC for improved performance, with dedicated source code under src/iocore/net/quic, making it future-proof for modern web standards.

Comprehensive Tooling

Provides tools like traffic_ctl for management and traffic_top for monitoring, detailed in the src directory, aiding in operational control and debugging.

Cons

Complex Build and Setup

Requires cmake configuration with specific dependencies (e.g., openssl, pcre2) and presets, making initial installation and compilation more involved compared to simpler proxies.

Steep Learning Curve

Configuration relies on files and command-line tools without a graphical interface, and plugin development demands C/C++ knowledge, limiting accessibility for non-experts.

Limited Beginner-Friendly Documentation

The README points to external wikis and mailing lists, but lacks comprehensive tutorials, assuming prior experience with high-performance proxy systems.

Frequently Asked Questions

Related Projects

Kong

🦍 The API and AI Gateway

Cloud-native high-performance edge/middle/service proxy

A library for building fast, reliable and evolvable network services.

Stars26,795

Forks1,663

Last commit4 days ago

zuul

Zuul is a gateway service that provides dynamic routing, monitoring, resiliency, security, and more.

Stars14,020

Forks2,437

Last commit5 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub