Need advice about which tool to choose?Ask the StackShare community!
Apache HTTP Server vs JBoss: What are the differences?
Developers describe Apache HTTP Server as "The most popular web server on the Internet since April 1996". 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. On the other hand, JBoss is detailed as "An open-source Java EE-based application server". An application platform for hosting your apps that provides an innovative modular, cloud-ready architecture, powerful management and automation, and world class developer productivity.
Apache HTTP Server and JBoss belong to "Web Servers" category of the tech stack.
Apache HTTP Server is an open source tool with 2.21K GitHub stars and 657 GitHub forks. Here's a link to Apache HTTP Server's open source repository on GitHub.
Slack, MIT, and Intuit are some of the popular companies that use Apache HTTP Server, whereas JBoss is used by Kanteron Systems, Syonet, and Tarya P2P. Apache HTTP Server has a broader approval, being mentioned in 6193 company stacks & 1070 developers stacks; compared to JBoss, which is listed in 14 company stacks and 3 developer stacks.
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!

I would pick nginx over both IIS and Apace HTTP Server any day. Combine it with docker, and as you grow maybe even traefik, and you'll have a really flexible solution for serving http content where you can take sites and projects up and down without effort, easily move it between systems and dont have to handle any dependencies on your actual local machine.
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."

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.

I use nginx because its more flexible and easy to configure

I use Apache HTTP Server because it's intuitive, comprehensive, well-documented, and just works
I was in a situation where I have to configure 40 RHEL servers 20 each for Apache HTTP Server and Tomcat server. My task was to 1. configure LVM with required logical volumes, format and mount for HTTP and Tomcat servers accordingly. 2. Install apache and tomcat. 3. Generate and apply selfsigned certs to http server. 4. Modify default ports on Tomcat to different ports. 5. Create users on RHEL for application support team. 6. other administrative tasks like, start, stop and restart HTTP and Tomcat services.
I have utilized the power of ansible for all these tasks, which made it easy and manageable.
Pros of Apache HTTP Server
- Web server478
- Most widely-used web server305
- Virtual hosting218
- Fast148
- Ssl support138
- Since 199645
- Asynchronous28
- Robust5
- Proven over many years4
- Mature1
- Perfect Support1
- Perfomance1
- Many available modules0
- Many available modules0
Pros of JBoss
Sign up to add or upvote prosMake informed product decisions
Cons of Apache HTTP Server
- Hard to set up3