Apache Web Server Reviews

I mainly use the product for hosting websites, content delivery, and virtual hosting.

I have been using  Apache to host my clients' web-based applications on the Internet for many years. Throughout this time, Apache has proven to be incredibly reliable, and everything has operated smoothly without encountering any issues. 

The web server has been highly valuable, stable, and it has been bug-free.

In terms of improvement, Apache should work better with modern cloud and proxy systems like Kubernetes. Right now, it is not very compatible with them. Additionally, adding a reverse proxy to Apache Web Server would be a significant improvement.

I have been using Apache Web Server for quite some time.

It is a very stable product. I would give it a ten out of ten for stability.

Scalability is a huge problem for Apache. I would rate it a one out of ten.

Apache has good community support, but there is a lack of corporate support options.

The initial setup is simple.

I have definitely seen ROI with Apache.

Apache is free.

I would definitely recommend Apache Web Server to anyone who is considering using it. Overall, I would rate it a ten out of ten.

I use Apache Web Server to build websites.

Apache Web Server is free of cost.

The product's initial setup process could be easier for users. 

We are using Apache Web Server’s version 2.4.57.

I rate the platform’s stability a ten out of ten.

Apache Web Server’s initial setup process is complex for users. However, it is straightforward for server administrators. It takes a few minutes to complete.

We have implemented the product with the help of our in-house team.

There is no licensing cost for the product. It is free to use.

I rate Apache Web Server a ten out of ten. I did an online course to learn how to use the product. I recommend it to users who want to build websites.

We use it for all our web deployments, making it our preferred choice across various projects.

The most significant advantage is the ability to swiftly enable HTTPS services when my DNS is configured correctly. This quick resolution and high performance are immensely beneficial for our operations.

By optimizing the infrastructure to allow the webserver to directly handle queries from memory—particularly by prioritizing the storage of queries in memory and processing them through the web server interface—I could potentially cut down the required instances from five hundred to two hundred. This optimization represents substantial savings, eliminating the need for deploying three hundred web servers. If we consider a time-saving of, for instance, half an hour per web server, this efficiency enhancement not only boosts performance but also decreases the total number of web server deployments.

I have been working with it for approximately fourteen years.

It's an extremely reliable web server that performs its tasks exceptionally well.

The server effortlessly scales up by spinning up new instances, making continuous operations and tasks more manageable.

The deployment process typically takes around eight minutes.

The return on investment is evident in the significant reduction in time to market and rollout. Even a saving of twenty minutes or half an hour per web server makes a notable impact.

In terms of competition, there's NGINX. It also performs admirably, and the two are quite comparable. Some individuals even rate NGINX higher than Apache.

Overall, I would rate it seven out of ten.

I have used it for PHP web servers and also as a proxy for Java application servers. I have used the Apache model for the Java infrastructure.

Its community is its most valuable feature. Solving problems is easier on Apache because so many people know this product. It's the most iconic, used web server in the world that I know.

The improvement can be done in the versions. Even though there are newer, stabler versions available, if you are installing from a data center, you have to install the older version. Then, installing the newer version is uncomfortable as it has to be done manually.

A monitoring interface would be great for this product. The monitoring dashboards for Apache's models are not included in the basic installation. You can install the basic monitoring model, then connect this model to another monitoring system.

Five years.

It is stable.

With Apache, you can't update the system. There is a big gap between models. I don't like this.

You can do it in a cluster configuration, and it is very scalable.

We have 5,000 users.

I have not used the technical support.

I have used a number of servers. Previously, I used NGINX. I switched to Apache because it has model and is more flexible.

The initial setup is easy.

It took 15 minutes to deploy.

I deployed the solution myself.

I would recommend the solution to others.

I would rate this solution as a nine (out of 10).

The solution's most valuable feature is its ability to run multiple ports on various platforms of the application with ease.

The solution's stability needs improvement.

I have been using the solution for seven years.

I rate its stability as an eight. It could be even better.

It is a scalable solution.

The solution's initial setup was straightforward. It also provides a cross-platform deployment to run it on Linux and Windows. As a beginner, the installation process took me two days to complete. But it was much easier later as I got exceptionally equipped with it. Also, deploying it on a standalone system takes a lot of work. Comparatively, I found it easy to deploy it as a module using XAMPP.

We implemented the solution in-house.

We don't have to pay for the solution's license. It is an open-source tool.

I rate the solution as an eight.

I have two use cases for Web Server; the first is for my personal use which is developing websites and the second is for the company where we provide solutions support. We are customers of Web Server and I'm a management consultant. 

The solution is open source, reliable, configurable and it's mostly secure. 

I think there are some features that could potentially be improved in Apache App Store. I'd also like to see some cloud solutions integrated with Web Server. 

I've been using this solution for 20 years. 

The initial setup is straightforward. 

I rate this solution eight out of 10. 

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.

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.

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.

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.

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.

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.

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.

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.

There is no licensing cost because it is open source.

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.

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.