Apache Web Server Reviews

I was administering the web server. 

Most of the features I liked were related to the performance during peak hours. Because I needed to optimize the Apache web server to run it as a high performer during my customers' usage, then I needed to reduce my Apache web server resource usage for that. So that part of the thing is what I was more interested in doing.

So, I mainly liked the performance and security.

I use the solution in my company as a base server. Many of our company's applications are hosted on Apache Web Server. As an open-source WAF, my company uses Apache Web Server with ModSecurity. My company also uses Apache Web Server as a proxy manager.

The most valuable features of the solution stem from the installation part and configuration manager that I use the most.

Our primary use is as a web server, but we have other uses and how it is deployed depends on our scenario. We have 40 websites that are related to our company now, and for some of them, we have a serious problem with threats, attacks, and preventing the attacks. Because of this we often use Apache. The throughput is important for us. The locks and the reports are really important for us. Because of this, we install a Web Server with the ability to handle the reports and analysis.  

Depending on the situation and the scenario, we use different solutions. For example, with our switches, our choices depend on the access layers. In most scenarios, we have these four layers: access, distribution, aggregation, and core. If for the access layer we decide we are going to use Cisco. For the distribution layer, again we use Cisco, either the C9500 or C9300 depending on what we have planned to use it for. For the aggregation, we are going to use something from the Nexus line. The model depends on the throughput that is expected and the other choices we make. For the core, of course, again Cisco. But the model always depends on the throughput and the scenario in which we are going to use it. The C9600 is suitable for the more demanding scenarios.  

If we are going to do access with IUC (Cisco Unity Connection architecture), we are going to use a C9300 or if it is not so important for us to be so robust, we are going to use the 2960 Cisco Station. For distribution layers that use an IUC system or something that needs lots of features, we are going to use the C9500. But in some other cases, we will use the 3850 series for the distribution. For the aggregation, the throughput is calculated. We are going to use something from the Nexus series, but it depends on that throughput calculation. For the code layer, we are going to use Cisco again, but the model depends on the throughput and the scenario. If we want, we sometimes choose a different part number.  

Sometimes in the past, I had also used Huawei switches, but we mostly used them several years ago. In some situations where we calculate the throughput, it may not be suitable. For most of the projects in our country, we have limitations and regulations that control some of what we deploy. Because of that Cisco is a good solution for us. If you have limitations for providing equipment like shipping regulations or the other problems with export, we might be able to use the Huawei switches. It depends on the features, the regulations, and the throughput. They are good. I think they are very good. But now we mostly use Cisco even when we could also go with Huawei for a project.  

I think the speed and traffic handling are the most important things. It is also more secure to use Apache and will have fewer problems than other web services.  

We primarily use the solution to deploy the web applications we have.

The solution is very secure.

It is free to use. The solution is open-source.

We've been satisfied with the solution. 

The setup is easy.

It is scalable.

The solution has been stable.

There are lots of documentation available online.

I mainly use it for website development. I have many websites and just stick with whatever version comes with my hosting platform.

The control panel is very easy to navigate. It's similar to most hosting platforms, so it's user-friendly. Once you get used to it, managing your hosting becomes easy, too.

Apache Web Server can be used to host applications. Apache Web Server is also famously called an HTTP server which can be used in both Linux and Windows. The product has already been in the industry for 25 years. When an individual installs the Linux operating system, Apache Web Server comes in-built. But the solution can also be installed directly without any cost. 

Apache Web Server is itself a complete product for applications. There are endless features in the solution. The HTTP server characteristics of the solution are a vital feature. The Apache Web Server can be used to create an in-house application server. The product can also be used to build a website. WordPress and PHP sites also require Apache Web Server to operate. 

Apache Web Server can be used as a proxy server and some applications can only run on an Apache Web Server. 

We use it for hosting applications.

The open-source nature is one of its most significant advantages. As a community-driven product, it captures the collective knowledge of developers. Any challenges that arise are typically resolved within a short period, thanks to the readily available solutions from the community.