Alternatives to Apache HTTP Server logo

Alternatives to Apache HTTP Server

Apache Tomcat, nginx, JBoss, Jetty, and Microsoft IIS are the most popular alternatives and competitors to Apache HTTP Server.
45.1K
7K
+ 1
1.4K

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

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

Apache HTTP Server alternatives & related posts

Apache Tomcat logo

Apache Tomcat

4.9K
2.9K
195
4.9K
2.9K
+ 1
195
An open source software implementation of the Java Servlet and JavaServer Pages technologies
Apache Tomcat logo
Apache Tomcat
VS
Apache HTTP Server logo
Apache HTTP Server

related Apache Tomcat posts

Java
Java
Spring
Spring
JUnit
JUnit
Apache HTTP Server
Apache HTTP Server
Apache Tomcat
Apache Tomcat
MySQL
MySQL

Java Spring JUnit

Apache HTTP Server Apache Tomcat

MySQL

See more
nginx logo

nginx

55.5K
13.8K
5.4K
55.5K
13.8K
+ 1
5.4K
A high performance free open source web server powering busiest sites on the Internet.
nginx logo
nginx
VS
Apache HTTP Server logo
Apache HTTP Server

related nginx posts

Docker
Docker
Docker Compose
Docker Compose
Jenkins
Jenkins
Kubernetes
Kubernetes
Amazon EC2
Amazon EC2
Heroku
Heroku
FeathersJS
FeathersJS
Node.js
Node.js
ExpressJS
ExpressJS
PostgreSQL
PostgreSQL
React
React
Redux
Redux
Semantic UI React
Semantic UI React
AVA
AVA
ESLint
ESLint
nginx
nginx
GitHub
GitHub
#Containerized
#Containers
#Backend
#Stack
#Frontend

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
Chris McFadden
Chris McFadden
VP, Engineering at SparkPost · | 7 upvotes · 79.5K views
atSparkPostSparkPost
nginx
nginx
OpenResty
OpenResty
Lua
Lua

We use nginx and OpenResty as our API proxy running on EC2 for auth, caching, and some rate limiting for our dozens of microservices. Since OpenResty support embedded Lua we were able to write a custom access module that calls out to our authentication service with the resource, method, and access token. If that succeeds then critical account info is passed down to the underlying microservice. This proxy approach keeps all authentication and authorization in one place and provides a unified CX for our API users. Nginx is fast and cheap to run though we are always exploring alternatives that are also economical. What do you use?

See more
JBoss logo

JBoss

73
31
0
73
31
+ 1
0
An open source Java EE-based application server
    Be the first to leave a pro
    JBoss logo
    JBoss
    VS
    Apache HTTP Server logo
    Apache HTTP Server
    Jetty logo

    Jetty

    308
    143
    41
    308
    143
    + 1
    41
    An open-source project providing an HTTP server, HTTP client, and javax.servlet container
    Jetty logo
    Jetty
    VS
    Apache HTTP Server logo
    Apache HTTP Server
    OpenResty logo

    OpenResty

    2.1K
    80
    0
    2.1K
    80
    + 1
    0
    Turning Nginx into a Full-fledged Web App Server
      Be the first to leave a pro
      OpenResty logo
      OpenResty
      VS
      Apache HTTP Server logo
      Apache HTTP Server

      related OpenResty posts

      Chris McFadden
      Chris McFadden
      VP, Engineering at SparkPost · | 7 upvotes · 79.5K views
      atSparkPostSparkPost
      nginx
      nginx
      OpenResty
      OpenResty
      Lua
      Lua

      We use nginx and OpenResty as our API proxy running on EC2 for auth, caching, and some rate limiting for our dozens of microservices. Since OpenResty support embedded Lua we were able to write a custom access module that calls out to our authentication service with the resource, method, and access token. If that succeeds then critical account info is passed down to the underlying microservice. This proxy approach keeps all authentication and authorization in one place and provides a unified CX for our API users. Nginx is fast and cheap to run though we are always exploring alternatives that are also economical. What do you use?

      See more
      Prometheus
      Prometheus
      Logstash
      Logstash
      nginx
      nginx
      OpenResty
      OpenResty
      Lua
      Lua
      Go
      Go

      At Kong while building an internal tool, we struggled to route metrics to Prometheus and logs to Logstash without incurring too much latency in our metrics collection.

      We replaced nginx with OpenResty on the edge of our tool which allowed us to use the lua-nginx-module to run Lua code that captures metrics and records telemetry data during every request’s log phase. Our code then pushes the metrics to a local aggregator process (written in Go) which in turn exposes them in Prometheus Exposition Format for consumption by Prometheus. This solution reduced the number of components we needed to maintain and is fast thanks to NGINX and LuaJIT.

      See more
      LiteSpeed logo

      LiteSpeed

      1.7K
      9
      0
      1.7K
      9
      + 1
      0
      A drop-in Apache replacement and the leading high-performance, high-scalability server
        Be the first to leave a pro
        LiteSpeed logo
        LiteSpeed
        VS
        Apache HTTP Server logo
        Apache HTTP Server
        Gunicorn logo

        Gunicorn

        625
        287
        58
        625
        287
        + 1
        58
        A Python WSGI HTTP Server for UNIX
        Gunicorn logo
        Gunicorn
        VS
        Apache HTTP Server logo
        Apache HTTP Server

        related Gunicorn posts

        Gunicorn
        Gunicorn
        uWSGI
        uWSGI
        Heroku
        Heroku
        AWS Elastic Beanstalk
        AWS Elastic Beanstalk

        I use Gunicorn because does one thing - it’s a WSGI HTTP server - and it does it well. Deploy it quickly and easily, and let the rest of your stack do what the rest of your stack does well, wherever that may be.

        uWSGI “aims at developing a full stack for building hosting services” - if that’s a thing you need then ok, but I like the principle of doing one thing well, and I deploy to platforms like Heroku and AWS Elastic Beanstalk where the rest of the “hosting service” is provided and managed for me.

        See more
        Cowboy logo

        Cowboy

        583
        25
        15
        583
        25
        + 1
        15
        Small, fast, modular HTTP server written in Erlang.
        Cowboy logo
        Cowboy
        VS
        Apache HTTP Server logo
        Apache HTTP Server
        Unicorn logo

        Unicorn

        479
        297
        292
        479
        297
        + 1
        292
        Rack HTTP server for fast clients and Unix
        Unicorn logo
        Unicorn
        VS
        Apache HTTP Server logo
        Apache HTTP Server

        related Unicorn posts

        Simon Bettison
        Simon Bettison
        Managing Director at Bettison.org Limited · | 6 upvotes · 106K views
        atBettison.org LimitedBettison.org Limited
        PostgreSQL
        PostgreSQL
        Elasticsearch
        Elasticsearch
        Sidekiq
        Sidekiq
        Redis
        Redis
        Amazon ElastiCache
        Amazon ElastiCache
        Rails
        Rails
        RSpec
        RSpec
        Selenium
        Selenium
        Travis CI
        Travis CI
        Ruby
        Ruby
        Unicorn
        Unicorn
        nginx
        nginx
        Amazon CloudFront
        Amazon CloudFront
        Amazon SES
        Amazon SES
        Amazon SQS
        Amazon SQS
        Amazon Route 53
        Amazon Route 53
        Amazon VPC
        Amazon VPC
        Docker
        Docker
        Amazon EC2 Container Service
        Amazon EC2 Container Service

        In 2010 we made the very difficult decision to entirely re-engineer our existing monolithic LAMP application from the ground up in order to address some growing concerns about it's long term viability as a platform.

        Full application re-write is almost always never the answer, because of the risks involved. However the situation warranted drastic action as it was clear that the existing product was going to face severe scaling issues. We felt it better address these sooner rather than later and also take the opportunity to improve the international architecture and also to refactor the database in. order that it better matched the changes in core functionality.

        PostgreSQL was chosen for its reputation as being solid ACID compliant database backend, it was available as an offering AWS RDS service which reduced the management overhead of us having to configure it ourselves. In order to reduce read load on the primary database we implemented an Elasticsearch layer for fast and scalable search operations. Synchronisation of these indexes was to be achieved through the use of Sidekiq's Redis based background workers on Amazon ElastiCache. Again the AWS solution here looked to be an easy way to keep our involvement in managing this part of the platform at a minimum. Allowing us to focus on our core business.

        Rails ls was chosen for its ability to quickly get core functionality up and running, its MVC architecture and also its focus on Test Driven Development using RSpec and Selenium with Travis CI providing continual integration. We also liked Ruby for its terse, clean and elegant syntax. Though YMMV on that one!

        Unicorn was chosen for its continual deployment and reputation as a reliable application server, nginx for its reputation as a fast and stable reverse-proxy. We also took advantage of the Amazon CloudFront CDN here to further improve performance by caching static assets globally.

        We tried to strike a balance between having control over management and configuration of our core application with the convenience of being able to leverage AWS hosted services for ancillary functions (Amazon SES , Amazon SQS Amazon Route 53 all hosted securely inside Amazon VPC of course!).

        Whilst there is some compromise here with potential vendor lock in, the tasks being performed by these ancillary services are no particularly specialised which should mitigate this risk. Furthermore we have already containerised the stack in our development using Docker environment, and looking to how best to bring this into production - potentially using Amazon EC2 Container Service

        See more
        Jerome Dalbert
        Jerome Dalbert
        Senior Backend Engineer at StackShare · | 6 upvotes · 36.4K views
        atStackShareStackShare
        Unicorn
        Unicorn
        Puma
        Puma
        Rails
        Rails

        We switched from Unicorn (process model) to Puma (threaded model) to decrease the memory footprint of our Rails production web server. Memory indeed dropped from 6GB to only 1GB!

        We just had to decrease our worker count and increase our thread count instead. Performance (response time and throughput) remained the same, if not slightly better. We had no thread-safety errors, which was good.

        Free bonus points are:

        • Requests are blazing fast on our dev and staging environments!
        • Puma has first-class support for WebSockets, so we know for sure that Rails ActionCable or GraphQL subscriptions will work great.
        • Being on Puma makes us even more "default Rails"-compliant since it is the default Rails web server these days.
        See more

        related Puma posts

        Jerome Dalbert
        Jerome Dalbert
        Senior Backend Engineer at StackShare · | 6 upvotes · 36.4K views
        atStackShareStackShare
        Unicorn
        Unicorn
        Puma
        Puma
        Rails
        Rails

        We switched from Unicorn (process model) to Puma (threaded model) to decrease the memory footprint of our Rails production web server. Memory indeed dropped from 6GB to only 1GB!

        We just had to decrease our worker count and increase our thread count instead. Performance (response time and throughput) remained the same, if not slightly better. We had no thread-safety errors, which was good.

        Free bonus points are:

        • Requests are blazing fast on our dev and staging environments!
        • Puma has first-class support for WebSockets, so we know for sure that Rails ActionCable or GraphQL subscriptions will work great.
        • Being on Puma makes us even more "default Rails"-compliant since it is the default Rails web server these days.
        See more
        Caddy logo

        Caddy

        122
        40
        7
        122
        40
        + 1
        7
        The HTTP/2 Web Server with Automatic HTTPS
        Caddy logo
        Caddy
        VS
        Apache HTTP Server logo
        Apache HTTP Server

        related Caddy posts

        Scott Mebberson
        Scott Mebberson
        CTO / Chief Architect at Idearium · | 5 upvotes · 29.2K views
        nginx
        nginx
        Caddy
        Caddy

        We used to primarily use nginx for our static web server and proxy in-front of Node.js. Now, we use Caddy. And we couldn't be happier.

        Caddy is simpler on all fronts. Configuration is easier. Free HTTPS out of the box. Some fantastic plugins. And for the most part, it's fast.

        Don't get me wrong, it's not lost on me that Nginx is actually a superior product.

        But for the times when you don't need that extra performance, and complexity - take a look at Caddy.

        See more
        lighttpd logo

        lighttpd

        103
        29
        23
        103
        29
        + 1
        23
        A secure, fast, compliant, and very flexible web-server that has been optimized for high-performance environments
        lighttpd logo
        lighttpd
        VS
        Apache HTTP Server logo
        Apache HTTP Server
        Wildfly logo

        Wildfly

        72
        25
        2
        72
        25
        + 1
        2
        A Java EE8 Application Server
        Wildfly logo
        Wildfly
        VS
        Apache HTTP Server logo
        Apache HTTP Server
        NGINX Unit logo

        NGINX Unit

        55
        57
        0
        55
        57
        + 1
        0
        A dynamic web and application server with Go, PHP, Python, Perl, and Ruby support.
          Be the first to leave a pro
          NGINX Unit logo
          NGINX Unit
          VS
          Apache HTTP Server logo
          Apache HTTP Server
          Oracle Weblogic Server logo

          Oracle Weblogic Server

          42
          16
          0
          42
          16
          + 1
          0
          JEE Application Server
            Be the first to leave a pro
            Oracle Weblogic Server logo
            Oracle Weblogic Server
            VS
            Apache HTTP Server logo
            Apache HTTP Server
            Sanic logo

            Sanic

            41
            39
            7
            41
            39
            + 1
            7
            Python 3.5+ web server that's written to go fast
            Sanic logo
            Sanic
            VS
            Apache HTTP Server logo
            Apache HTTP Server
            GlassFish logo

            GlassFish

            36
            19
            0
            36
            19
            + 1
            0
            The Open Source Java EE Reference Implementation
              Be the first to leave a pro
              GlassFish logo
              GlassFish
              VS
              Apache HTTP Server logo
              Apache HTTP Server
              Websphere logo

              Websphere

              32
              13
              0
              32
              13
              + 1
              0
              Application and integration middleware
                Be the first to leave a pro