Alternatives to Apache Traffic Server logo

Alternatives to Apache Traffic Server

HAProxy, Varnish, Squid, NGINX, and Apache HTTP Server are the most popular alternatives and competitors to Apache Traffic Server.
449
41
+ 1
0

What is Apache Traffic Server and what are its top alternatives?

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
Apache Traffic Server is a tool in the Web Cache category of a tech stack.
Apache Traffic Server is an open source tool with 1.4K GitHub stars and 706 GitHub forks. Here’s a link to Apache Traffic Server's open source repository on GitHub

Top Alternatives to Apache Traffic Server

  • HAProxy

    HAProxy

    HAProxy (High Availability Proxy) is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. ...

  • 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. ...

  • Squid

    Squid

    Squid reduces bandwidth and improves response times by caching and reusing frequently-requested web pages. Squid has extensive access controls and makes a great server accelerator. It runs on most available operating systems, including Windows and is licensed under the GNU GPL. ...

  • NGINX

    NGINX

    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. ...

  • 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. ...

  • Section

    Section

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

  • Nuster

    Nuster

    nuster is a high performance HTTP proxy cache server and RESTful NoSQL cache server based on HAProxy. ...

Apache Traffic Server alternatives & related posts

HAProxy logo

HAProxy

2.2K
1.9K
553
The Reliable, High Performance TCP/HTTP Load Balancer
2.2K
1.9K
+ 1
553
PROS OF HAPROXY
  • 130
    Load balancer
  • 100
    High performance
  • 69
    Very fast
  • 57
    Proxying for tcp and http
  • 55
    SSL termination
  • 30
    Open source
  • 27
    Reliable
  • 20
    Free
  • 18
    Well-Documented
  • 12
    Very popular
  • 7
    Suited for very high traffic web sites
  • 7
    Runs health checks on backends
  • 6
    Scalable
  • 5
    Ready to Docker
  • 4
    Powers many world's most visited sites
  • 2
    Simple
  • 2
    Work with NTLM
  • 2
    Ssl offloading
CONS OF HAPROXY
  • 3
    Becomes your single point of failure

related HAProxy posts

Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.

See more
Tom Klein

We're using Git through GitHub for public repositories and GitLab for our private repositories due to its easy to use features. Docker and Kubernetes are a must have for our highly scalable infrastructure complimented by HAProxy with Varnish in front of it. We are using a lot of npm and Visual Studio Code in our development sessions.

See more
Varnish logo

Varnish

11.4K
1.8K
359
High-performance HTTP accelerator
11.4K
1.8K
+ 1
359
PROS OF VARNISH
  • 103
    High-performance
  • 66
    Very Fast
  • 56
    Very Stable
  • 43
    Very Robust
  • 36
    HTTP reverse proxy
  • 20
    Open Source
  • 17
    Web application accelerator
  • 10
    Easy to config
  • 4
    Widely Used
  • 3
    Great community
  • 1
    Essential software for HTTP
CONS OF VARNISH
    Be the first to leave a con

    related Varnish posts

    Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.

    See more
    Tom Klein

    We're using Git through GitHub for public repositories and GitLab for our private repositories due to its easy to use features. Docker and Kubernetes are a must have for our highly scalable infrastructure complimented by HAProxy with Varnish in front of it. We are using a lot of npm and Visual Studio Code in our development sessions.

    See more
    Squid logo

    Squid

    85
    161
    17
    A caching proxy for the Web supporting HTTP, HTTPS, FTP, and more
    85
    161
    + 1
    17
    PROS OF SQUID
    • 4
      Easy to config
    • 2
      Cluster
    • 2
      Very Fast
    • 2
      Web application accelerator
    • 1
      Widely Used
    • 1
      Great community
    • 1
      ESI
    • 1
      ICP
    • 1
      High-performance
    • 1
      Very Stable
    • 1
      Open Source
    • 0
      Qq
    CONS OF SQUID
      Be the first to leave a con

      related Squid posts

      NGINX logo

      NGINX

      94.3K
      44.5K
      5.5K
      A high performance free open source web server powering busiest sites on the Internet.
      94.3K
      44.5K
      + 1
      5.5K
      PROS OF NGINX
      • 1.4K
        High-performance http server
      • 896
        Performance
      • 728
        Easy to configure
      • 606
        Open source
      • 529
        Load balancer
      • 286
        Scalability
      • 285
        Free
      • 222
        Web server
      • 173
        Simplicity
      • 134
        Easy setup
      • 29
        Content caching
      • 19
        Web Accelerator
      • 14
        Capability
      • 13
        Fast
      • 11
        Predictability
      • 10
        High-latency
      • 7
        Reverse Proxy
      • 6
        Supports http/2
      • 4
        The best of them
      • 4
        Lots of Modules
      • 4
        Enterprise version
      • 4
        Great Community
      • 3
        High perfomance proxy server
      • 3
        Streaming media
      • 3
        Embedded Lua scripting
      • 3
        Reversy Proxy
      • 3
        Streaming media delivery
      • 2
        Fast and easy to set up
      • 2
        Lightweight
      • 2
        Slim
      • 2
        saltstack
      • 1
        Virtual hosting
      • 1
        Blash
      • 1
        GRPC-Web
      • 1
        Ingress controller
      • 1
        Narrow focus. Easy to configure. Fast
      • 1
        Along with Redis Cache its the Most superior
      • 0
        A
      CONS OF NGINX
      • 8
        Advanced features require subscription

      related NGINX posts

      Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

      We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

      See more
      Gabriel Pa
      Shared insights
      on
      TraefikTraefikNGINXNGINX
      at

      We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

      We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

      The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

      See more
      Apache HTTP Server logo

      Apache HTTP Server

      59.2K
      18K
      1.4K
      The most popular web server on the Internet since April 1996
      59.2K
      18K
      + 1
      1.4K
      PROS OF APACHE HTTP SERVER
      • 477
        Web server
      • 305
        Most widely-used web server
      • 218
        Virtual hosting
      • 148
        Fast
      • 138
        Ssl support
      • 45
        Since 1996
      • 28
        Asynchronous
      • 5
        Robust
      • 4
        Proven over many years
      • 1
        Mature
      • 1
        Perfect Support
      • 1
        Perfomance
      • 0
        Many available modules
      • 0
        Many available modules
      CONS OF APACHE HTTP SERVER
      • 2
        Hard to set up

      related Apache HTTP Server posts

      Tim Abbott
      Shared insights
      on
      NGINXNGINXApache HTTP ServerApache HTTP Server
      at

      We've been happy with nginx as part of our stack. As an open source web application that folks install on-premise, the configuration system for the webserver is pretty important to us. I have a few complaints (e.g. the configuration syntax for conditionals is a pain), but overall we've found it pretty easy to build a configurable set of options (see link) for how to run Zulip on nginx, both directly and with a remote reverse proxy in front of it, with a minimum of code duplication.

      Certainly I've been a lot happier with it than I was working with Apache HTTP Server in past projects.

      See more
      Marcel Kornegoor
      Shared insights
      on
      NGINXNGINXApache HTTP ServerApache HTTP Server

      nginx or Apache HTTP Server that's the question. The best choice depends on what it needs to serve. In general, Nginx performs better with static content, where Apache and Nginx score roughly the same when it comes to dynamic content. Since most webpages and web-applications use both static and dynamic content, a combination of both platforms may be the best solution.

      Since both webservers are easy to deploy and free to use, setting up a performance or feature comparison test is no big deal. This way you can see what solutions suits your application or content best. Don't forget to look at other aspects, like security, back-end compatibility (easy of integration) and manageability, as well.

      A reasonably good comparison between the two can be found in the link below.

      See more
      Section logo

      Section

      51
      62
      62
      Run compute workloads on a distributed edge
      51
      62
      + 1
      62
      PROS OF SECTION
      • 10
        Realtime stats
      • 10
        Makes the hard parts of varnish easy
      • 8
        No more hair pulling configuring caching
      • 8
        Git support
      • 7
        Easy setup
      • 6
        Qa testing
      • 4
        Test Varnish Settings in Dev & Prod
      • 4
        Kibana logs
      • 3
        Graphite out of the box
      • 2
        Professional, rock solid platform, easy to user
      CONS OF SECTION
        Be the first to leave a con

        related Section posts

        Nuster logo

        Nuster

        3
        21
        11
        A high performance HTTP proxy cache server and RESTful NoSQL cache server based on HAProxy.
        3
        21
        + 1
        11
        PROS OF NUSTER
        • 2
          Easy to configure
        • 1
          High-performance
        • 1
          Web cache
        • 1
          Web application accelerator
        • 1
          Very Fast
        • 1
          Open Source
        • 1
          Load balancer
        • 1
          Proxying for tcp and http
        • 1
          SSL termination
        • 1
          Free
        • 0
          HTTP reverse proxy
        CONS OF NUSTER
          Be the first to leave a con

          related Nuster posts