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.
47.9K
9.6K
+ 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.4K GitHub stars and 758 GitHub forks. Here鈥檚 a link to Apache HTTP Server's open source repository on GitHub

Top Alternatives of Apache HTTP Server

Apache HTTP Server alternatives & related posts

Apache Tomcat logo

Apache Tomcat

6.4K
4.3K
195
6.4K
4.3K
+ 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

62.4K
20.5K
5.4K
62.4K
20.5K
+ 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
Node.js
Node.js
Ubuntu
Ubuntu
MySQL
MySQL
npm
npm
Framework7
Framework7
Vue.js
Vue.js
Webpack
Webpack
nginx
nginx
#Lenovo
#HapiJS
#Framework7
#Plaid

I just designed, developed, and deployed my own budgeting app, dailybudget.cc, which allows me to automate my budgeting the way I have always done it, in a way that I could never fully capture with other budgeting apps, such as Mint, EveryDollar, or YNAB. I spent 4 years from the time I first had the idea to the time I actually sat down to design it and start development. During this time I evaluated many other budgeting app solutions, and had even architected a prototype that I never ended up using. But boy, have technologies come much further in 4 years.

Though my first prototype used Java and Tomcat, I completely abandoned those 4 years later in favor of Node.js technologies, which I have found are equally as stable, more flexible (for better or for worse), and capable of significantly more rapid development. Since what I have deployed now is in beta and is primarily for limited user use, I favored rapid development over slower development where I would write more automated unit tests. I chose to build the app as a HTML5 web application (rather than native iOS or Android, for now), and I used a separated API backend/Web frontend model. My target platform for use with the app is mobile handheld touch devices, though it can work on any laptop or desktop with a touchscreen. Given these design targets, many of the technologies I chose were because of familiarity with them as well as a strong online community, and some technologies I chose that I had to learn anew, because they appeared to fit my needs.

My entire app runs on a #lenovo IdeaCentre desktop on my home network, on which I have installed Ubuntu 18.04. Ubuntu is something I have switched to after a long time of use and familiarity with RedHat Enterprise Linux and CentOS, because the online support for Ubuntu is now tremendous, and there is so much documentation and examples online of how to configure and use Ubuntu; not to mention I have not been thrilled with the direction new releases of CentOS. Ubuntu is also a good environment for development - it is so easy to follow the many online examples. Lastly, I may migrate my app and configuration to Amazon AWS, which also uses Ubuntu for its EC2 Linux VMs, so having Ubuntu now is helpful for that prospect.

The API backend uses Node.js, with #HapiJS as the API server framework and MySQL as my persistence database. HapiJS is something I have had familiarity with and is just a phenomenal framework to plug into and configure, especially if you use it for a route-based API. #Mysql has a great online community. I could've used PostgreSQL too, but I am more familiar with MySQL. Also, if I migrate to Amazon AWS, Amazon's RDS uses MySQL. I use npm as a one-stop-shop package manager and environment manager.

The Web frontend uses a combination of Framework7 and Vue.js. I cannot evangelize Framework7 enough! It is a fantasic tool by @nolimits4web (GitHub) that is really easy to use, really well thought out, and really performant. Framework7 simulates the native iOS or Android (Google Material) experiences, all using HTML5 constructs (HTML+CSS+JS). Vue.js is another very fantastic binding and frontend framework which has a good online community and is well documented and easy to use. I had to choose between VueJS and ReactJS, and ultimately chose VueJS over ReactJS because it seemed to favor more rapid development with less ramp-up time, whereas I understood ReactJS to be more of an enterprise level framework (though still good for smaller projects like mine). When using Framework7 with VueJS, NodeJS is used along with Webpack to transpile my code into browser-friendly JavaScript, HTML, etc. Webpack was nice to use because it has a hot-deploy development mode to enable rapid development without me having stop, recompile, and start my server (this was one of several reasons against using Java with Tomcat). I had no familiarity with Framework7, VueJS, or Webpack prior to this project.

I use nginx as my web server and have the API running behind a reverse proxy, and all of the web frontent content hosted as static content.

I use the plaid API to sync my bank transactions to my database. This is another fantastic framework (though not free beyond development use) that it turns out is extremely easy to use for the complex job that it solves.

See more
JBoss logo

JBoss

101
76
0
101
76
+ 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

    321
    173
    42
    321
    173
    + 1
    42
    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
    99
    2
    2.1K
    99
    + 1
    2
    Turning Nginx into a Full-fledged Web App Server
    OpenResty logo
    OpenResty
    VS
    Apache HTTP Server logo
    Apache HTTP Server

    related OpenResty posts

    Chris McFadden
    Chris McFadden
    VP, Engineering at SparkPost | 7 upvotes 174.3K 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鈥檚 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.8K
    21
    0
    1.8K
    21
    + 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