Apache Web Server OverviewUNIXBusinessApplication

Apache Web Server is the #8 ranked solution in top Application Infrastructure tools. PeerSpot users give Apache Web Server an average rating of 7.6 out of 10. Apache Web Server is most commonly compared to IIS: Apache Web Server vs IIS. Apache Web Server is popular among the large enterprise segment, accounting for 67% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 16% of all views.
Buyer's Guide

Download the Application Infrastructure Buyer's Guide including reviews and more. Updated: November 2022

What is Apache Web Server?

The Apache HTTP Server Project was founded in 1995 by a group of webmasters, known as The Apache Group, with the aim of developing robust, richly-featured, freely-available and commercial-standard Web (HTTP) server source code. The result was Apache Web Server or Apache HTTP Server, which is an open-source public-domain web server.

This collaborative project has been enhanced ever since with contributions from the core development team and other volunteers situated all over the globe. Also, hundreds of users of this open-source web server have contributed code, ideas, and documentation. The project falls under The Apache Software Foundation, which manages many open-source projects.

Apache Web Server was previously known as Apache HTTP Server.

Apache Web Server Customers
Cisco, Intuit, General Electric, Adobe, VMware, PayPal, HP, EMC, eBay, Apple, SAP, Qualcomm, SanDisk, Allstate, FedEx
Apache Web Server Video

Apache Web Server Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
System Administrator at Confidential
MSP
Top 5Leaderboard
Useful in deploying servers to host websites with good modularity
Pros and Cons
  • "It's very stable, and it hosts one of the biggest of many biggest web applications in the world."
  • "There is a security-related problem that depends on the web server's configuration."

What is our primary use case?

It is utilized as a simple web server, meaning you can configure it and use the HTTP or HTTPS protocol. This is the secure version of the HTTP protocol to host or manage the connections from users who want to access the web application, from the internet, and from our local users.

What is most valuable?

The modularity of the application is good. It allows us to use a modular approach, meaning that not all features are hard-coded inside the application, but we can use modules so that these features can be enabled or disabled. If we don't want to use some features, we don't load or enable them inside the configuration file.

What needs improvement?

Nginx is another web server solution that can be used as an accelerator when you want a high-performance web server. Nginx can also be used as a reverse proxy and a cache server to accelerate the response times for all users. If we compare Nginx with Apache Web Server, Apache Web Server cannot be used when high performance is the key feature of your application. If we want to handle many users, choosing Nginx rather than the Apache Web Server is better. However, when you want to scale the application, it is not as good as Nginx and Nginx can handle more users than the Apache Web Server.

For how long have I used the solution?

We have been using this solution for a long time. We use it to deploy servers that host websites. We are using the latest version. It is deployed on-premises.

Buyer's Guide
Application Infrastructure
November 2022
Find out what your peers are saying about Apache, Microsoft, Zend and others in Application Infrastructure. Updated: November 2022.
657,397 professionals have used our research since 2012.

What do I think about the stability of the solution?

It's very stable, and it hosts one of the biggest of many biggest web applications in the world. It is used widely by many companies. Since they are still using it, I think it's still stable, and we don't have a problem with our application when they're using the Apache Web Server.

What do I think about the scalability of the solution?

Apache can be scalable, but not by using a native feature of Apache. Instead, you have to rely on other tools to set the scalability feature. This is the same for Nginx.

How are customer service and support?

They have community support. It's an organization that handles some open-source because Apache Web Server is a project handled and maintained by the company organization or the Apache Foundation. They maintain the source code and versions. We don't create a ticket with the Apache Foundation, but we will rely on a large community of experts.

How was the initial setup?

The initial setup was straightforward and depended on the operating system. If it's Windows, it is simple when installing. On Linux, it's also straightforward, especially if you want to use specific packages. For example, if you are using Central West Linux or Uganda, they provide a package specific to that distribution. So with a simple command, you can install the Apache Web Server, and all its dependencies will be installed as well.

The configuration is complicated compared to the installation. However, if you need a lot of knowledge about the HTTP protocol, how websites work, and how each module of Apache can work or talk with other modules, it is handled by the core service of the attachable server. The configuration is done by the person or department that deploys the application in the server, so they configure the Apache Web Server.

Maintaining requires two people, myself and another colleague. If another company develops an application, it will maintain the Apache Web Server. But we only maintain the operating system, installing updates and system configurations. But the maintenance of the Apache Web Server and the work application is made by that company, not us.

What's my experience with pricing, setup cost, and licensing?

There is no licensing cost because it is open source.

Which other solutions did I evaluate?

Regarding web services, two major web servers are available, IIS from Microsoft Windows and Apache Web Server. They are the most used web services all over the world. There is also Nginx. Each service has its scenarios of when it will be used. For small to medium size projects in an organization, they can use Apache Web Server or IIS, but if you want something very powerful, you can switch to Nginx.

What other advice do I have?

I rate this solution an eight out of ten. Regarding advice, there is a security-related problem that depends on the web server's configuration. If you install the web server, it works, and you can put your web application in a directory that Apache Web Server reads from to display the web application.

The default installation comes with a default configuration. With default configuration comes security flaws, so you need to set permissions in the configuration file in your website directory. Before you deploy your application with Apache Web Server, you need to know how to configure a web server, how the HTTP protocol works, and how communication between the client and the server works.

If you don't know how to configure everything in a web server, sometimes your server can hang unexpectedly. Sometimes your website won't work as expected, and you will create or offer malicious persons to have access to your web server. If they have access to the web server, they can access every server in the organization because the web server is like the front door. If it's properly secured, it will be difficult for malicious people to enter your organization, but bad things can happen if it's not very secure.

Regarding features, Apache offers a module that will change the behaviour of the Apache Web Server, including some security features that will protect your application from the most used web attacks. It will act like a web firewall where you configure your Apache Web server to protect your web application from widely used attacks on the web. The feature is called Security Mode. It's a module that you can install and act as a web firewall called the WAF (Web Application Firewall), which will not only serve the client but will check their request to see or detect if they are part of an initiated attack or not.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
VP at a computer software company with 201-500 employees
Real User
Top 5Leaderboard
Easy to use and quick to deploy with good security
Pros and Cons
  • "The solution offers good security."
  • "Things change very fast. We're always on the lookout for better approaches and tools. If the solution falls behind, we may have to switch."

What is our primary use case?

We primarily use the solution for deployment. We use it for our internet banking portal.

What is most valuable?

The solution is very stable. It comes with good flexibility as well.

We've found the product to be scalable.

It's a solution that's fairly easy to use.

The solution offers good security.

The product has good compatibility with other solutions.

What needs improvement?

I haven't really gone in deep in utilizing the full functionality of the product just yet. We just use it enough to run our application. There's probably a lot on the solution we haven't even tried. 

It's good enough to run and deploy our application. Therefore, I can't really speak to anything that is lacking.

Things change very fast. We're always on the lookout for better approaches and tools. If the solution falls behind, we may have to switch.

Nowadays, the user actually requests to do their own maintenance instead of relying on the vendor. We're looking for something that's easy to understand for the user so that they can do their own maintenance.

For how long have I used the solution?

I've been using the solution for about four or five years at this point. It's been a while.

What do I think about the stability of the solution?

The solution is extremely stable. We haven't had any issues with bugs or glitches and it doesn't crash or freeze. It's been reliable.

What do I think about the scalability of the solution?

The solution can scale if you need it to.

In our case, normally we don't do a lot of processing on the webserver. It's pretty lightweight usage.

We do pa=lan to continue to use the solution going forward.

How are customer service and technical support?

We rarely need technical support. We might need more support when it comes to the database, however, for the web server, it's pretty problem-free. We're satisfied with the support. That said, we rarely use it.

How was the initial setup?

The initial setup is not complex at all. We were able to very easily set up and deploy the solution. It was straightforward.

The deployment is very fast. Everything is smooth. The setting firewall, everything, is quick and then it just takes one or two hours to install it.

Since the setup is pretty easy, you only really need two people to deploy it.

What about the implementation team?

We handled the initial setup ourselves, in-house. It's relatively simple to set up, and therefore we didn't need the assistance of any integrators or consultants.

Normally we need a team to make sure the firewall is set up properly. Installation cannot work if the firewall is not available.

What's my experience with pricing, setup cost, and licensing?

We pay for the solution yearly. I cannot speak to the exact amount the organization pays as the licensing part of the solution isn't something I deal with directly.

Which other solutions did I evaluate?

We've tried a few different solutions. At the very beginning, we're using Tomcat Apache. After that, we switched to AWS, After AWS, we moved to this product and we've been with it ever since. 

What other advice do I have?

We're just a customer. We are an end-user of Apache.

We haven't done any recent upgrades and therefore aren't likely using the latest version of the solution currently.

So far we are still exploring to see what are the best or the more cost-effective tools for us to integrate as there are so many properties we need to integrate with different protocols. So, we are still exploring, looking for the best approach.

I'd recommend the solution.

Overall, I'd rate the solution at a seven out of ten. We've been mostly happy with that product so far.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Application Infrastructure Report and find out what your peers are saying about Apache, Microsoft, Zend, and more!
Updated: November 2022
Product Categories
Application Infrastructure
Buyer's Guide
Download our free Application Infrastructure Report and find out what your peers are saying about Apache, Microsoft, Zend, and more!