StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Platform as a Service
  4. Web Servers
  5. Apache Traffic Server vs nginx

Apache Traffic Server vs nginx

OverviewDecisionsComparisonAlternatives

Overview

NGINX
NGINX
Stacks115.0K
Followers61.9K
Votes5.5K
GitHub Stars28.4K
Forks7.6K
Apache Traffic Server
Apache Traffic Server
Stacks452
Followers57
Votes0
GitHub Stars1.9K
Forks842

Apache Traffic Server vs nginx: What are the differences?

Introduction

Here, we will discuss the key differences between Apache Traffic Server and nginx. These two popular web server software have several distinctions that set them apart from each other.

  1. Architecture: Apache Traffic Server (ATS) is designed as a reverse proxy cache, primarily focused on caching and accelerating content delivery. It operates as a separate proxy server between clients and web servers. In contrast, nginx is a lightweight web server and reverse proxy that aims to handle concurrent connections efficiently while providing features like load balancing, SSL support, and URL rewriting.

  2. Performance: Both ATS and nginx are known for their excellent performance, but they have different areas of expertise. ATS is particularly efficient in caching and handling static content, making it a strong choice for high-traffic websites. On the other hand, nginx excels in handling a large number of concurrent connections without consuming significant system resources, which makes it popular for serving dynamic content and processing requests quickly.

  3. Configuration: The configuration syntax and structure of ATS and nginx differ significantly. ATS uses a complex configuration system based on XML syntax, which allows for fine-grained control over its extensive set of features. In contrast, nginx uses a simpler configuration language based on a lightweight key-value format, making it easier to understand and manage for most users.

  4. Modules and Extensions: Both ATS and nginx support a wide range of modules and extensions to enhance their functionality. However, the availability and variety of modules differ. ATS offers a comprehensive set of built-in modules, including caching, traffic shaping, and URL routing. Furthermore, it allows developers to write custom modules to extend its capabilities. Nginx also provides a diverse set of modules, but it places greater emphasis on third-party modules created by the community, which can be easily added to the server's functionality.

  5. Community and Support: Nginx has gained significant popularity over the years, fostering a large and active community of users and developers. This extensive community support translates into numerous resources, tutorials, and plugins available for nginx users. Apache Traffic Server, although widely adopted in its own right, has a smaller community compared to nginx, resulting in a relatively lesser number of available resources.

  6. Licensing: ATS and nginx differ in their licensing terms. ATS is released under the Apache License, making it open source and free to use. Nginx, on the other hand, has a dual licensing model, offering both open source (2-clause BSD license) and commercial licenses. The commercial variant provides additional features and support options for enterprise users.

In summary, Apache Traffic Server and nginx offer robust web server solutions with their respective strengths. ATS excels in caching and static content delivery, while nginx is highly efficient in handling concurrent connections and dynamic content. The choice between them depends on specific requirements, architecture complexity, and community support.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on NGINX, Apache Traffic Server

greg00m
greg00m

Mar 9, 2020

Needs advice

I am diving into web development, both front and back end. I feel comfortable with administration, scripting and moderate coding in bash, Python and C++, but I am also a Windows fan (i love inner conflict). What are the votes on web servers? IIS is expensive and restrictive (has Windows adoption of open source changed this?) Apache has the history but seems to be at the root of most of my Infosec issues, and I know nothing about nginx (is it too new to rely on?). And no, I don't know what I want to do on the web explicitly, but hosting and data storage (both cloud and tape) are possibilities.
Ready, aim fire!

766k views766k
Comments
jlp78
jlp78

May 31, 2019

ReviewonNGINXNGINX

I use nginx because it is very light weight. Where Apache tries to include everything in the web server, nginx opts to have external programs/facilities take care of that so the web server can focus on efficiently serving web pages. While this can seem inefficient, it limits the number of new bugs found in the web server, which is the element that faces the client most directly.

727k views727k
Comments
StackShare
StackShare

May 29, 2019

Needs advice

From a StackShare Community member: "We are a LAMP shop currently focused on improving web performance for our customers. We have made many front-end optimizations and now we are considering replacing Apache with nginx. I was wondering if others saw a noticeable performance gain or any other benefits by switching."

725k views725k
Comments

Detailed Comparison

NGINX
NGINX
Apache Traffic Server
Apache Traffic Server

nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018.

It is a fast, scalable and extensible HTTP/1.1 and HTTP/2.0 compliant caching proxy server.Improve your response time, while reducing server load and bandwidth needs by caching and reusing frequently-requested web pages, images, and web ser

-
Open Source; Very Fast; High-performance; Extensible; ESI; Load Balancer; Caching
Statistics
GitHub Stars
28.4K
GitHub Stars
1.9K
GitHub Forks
7.6K
GitHub Forks
842
Stacks
115.0K
Stacks
452
Followers
61.9K
Followers
57
Votes
5.5K
Votes
0
Pros & Cons
Pros
  • 1453
    High-performance http server
  • 895
    Performance
  • 730
    Easy to configure
  • 607
    Open source
  • 530
    Load balancer
Cons
  • 10
    Advanced features require subscription
No community feedback yet
Integrations
No integrations available
CentOS
CentOS
FreeBSD
FreeBSD
Alpine Linux
Alpine Linux
Fedora
Fedora
Debian
Debian
Mac OS X
Mac OS X

What are some alternatives to NGINX, Apache Traffic Server?

Apache HTTP Server

Apache HTTP Server

The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet.

Varnish

Varnish

Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. Varnish Cache is really, really fast. It typically speeds up delivery with a factor of 300 - 1000x, depending on your architecture.

Unicorn

Unicorn

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients.

Microsoft IIS

Microsoft IIS

Internet Information Services (IIS) for Windows Server is a flexible, secure and manageable Web server for hosting anything on the Web. From media streaming to web applications, IIS's scalable and open architecture is ready to handle the most demanding tasks.

Apache Tomcat

Apache Tomcat

Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.

Passenger

Passenger

Phusion Passenger is a web server and application server, designed to be fast, robust and lightweight. It takes a lot of complexity out of deploying web apps, adds powerful enterprise-grade features that are useful in production, and makes administration much easier and less complex.

Gunicorn

Gunicorn

Gunicorn is a pre-fork worker model ported from Ruby's Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

Section

Section

Edge Compute Platform gives Dev and Ops engineers the access and control they need to run compute workloads on a distributed edge.

Jetty

Jetty

Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty.

lighttpd

lighttpd

lighttpd has a very low memory footprint compared to other webservers and takes care of cpu-load. Its advanced feature-set (FastCGI, CGI, Auth, Output-Compression, URL-Rewriting and many more) make lighttpd the perfect webserver-software for every server that suffers load problems.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot