Apache Web Server Reviews

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.

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

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.

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.

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

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.

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.

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.

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.

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.

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.

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. 

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.

On-premises

Depending on what operating system you are using, you can have a website up in no time using Apache web server. Very easy to install on multiple platforms.90% of our web servers are using Apache, I like the fact that there is no management interface, so that we can minimize system resources when it comes to large scale deployments.As Apache is opensource the community is great when it comes to documentation and troubleshooting problems.

If Apache master the ability of hosting websites/web apps that use Microsoft's .Net framework then it will definitely be the best web server to use.Internally we have both Microsoft IIS web servers and Apache web servers. We only use IIS for web sites that are developed in .net, for any other website written in php, perl, java (also many more) we use Apache.For anyone who is looking to host websites or proxy servers, I advise you to use Apache, also there's no cost - only for the hardware of the machine that you are running it from.

From experience I have found that Apache runs smoothly and a lot faster on Ubuntu.

I am currently using Apache Web Server and it is integrated with Apache JMeter and Tomcat. I run these solutions in a virtualized environment that is in a private cloud, on-premises.

We are a solution provider and our primary use case is creating web servers on core banking systems. 

The best thing about Apache is that it is open-source, so implementing my platform on-premises is less expansive than other solutions.

Better integration with other environments is needed.

It would be great if technical support for Apache were available in Iran. It is a very important need.

I have been working with Apache Web Server for ten years.

This is a stable solution. One of the people I know is the system administrator of some systems that I have deployed in the past, and those systems are stable today.

Being in Iran, we do not have access to technical support because of sanctions. However, we have been able to solve any problems ourselves.

The initial setup is straightforward. If you are just learning or reading about this solution, the decisions to make are not very complex.

The first point of using these services is that you have to use scripts for deploying the web servers on the systems. They can be effectively used in many platforms and deployed for heavy duties, but tuning and improving them requires some work. Automating with scripts will help to save some time.

My advice to anybody who is implementing this solution is to deploy it on a Linux-based server and follow the best practices. 

I would rate this solution an eight out of ten.

On-premises

The Apache Web Server is our software of choice for running our web servers for the past seven (7) years. It's clearly one of the best open-source projects in world, as its continuing existence and use is a testament to how great this software is.There have been numerous web server software that has come out in the recent years like Nginx and lhttpd, but the Apache web server has remained as the web server of choice for a lot of organizations world-wide.What I like about the Apache Web Server is that it just simply works. It's very easy to set-up and configure, and you can have a website up in a few minutes. Furthermore, it supports a lot of web scripting languages which even made it more popular.

The only thing that gives me a frown about the Apache Web Server is the command-line configuration. Though it can be configured via web control panels like webmin, you really have to dig deep into the configuration files to really make apache work.The Apache Web Server is undoubtedly one of the best web server software in the world. What's even better is that it's free and remains free even after years of existing. Truly one of the most successful open-source projects ever.

For simple websites, the Apache web server is easy to install and configure. It can even be configured with web hosting panels. However, configuring the Apache web server from the command line is recommended for complex applications like virtual hosting.

The Software is free. A few important features in the long list include: stability - it's continuously supported by the open source community, reducing the bugs and errors. portability - Apache is available for multiple OS Customizability - custom modules can be built easily. Efficient handling of client requests. Most popular webserver on the internet.

No support is available from Apache software foundation. Apache needs fine tuning of its components when in a larger environment, otherwise it can make your server unresponsive.

The webserver survey showed by netcraft [netcraft.com] says, "Apache is still the most widely used [61%] webserver in the world of internet." Apache is designed in such a way that different components of the system can be connected together easily. The beauty is that you can replace or add a component or feature without affecting the system. Apache is a powerful tool with which you can make it do just about anything you need. As there are multiple masterminds taking caring of Apache, it will remain the king of webservers for long!