Running and keeping secure custom PHP-based internal business applications.I have been using apache for years to build my custom PHP and MySQL applications and the long-term stability I have never known. What I love the most is that it comes out of the box very well when used in a classic "LAMP" setup. We often times need to apply a full range of in-house tools and simply uploading an .htaccess file to a given folder to handle a rewrite of the URLs or prevent access is a tremendous timesaver. It allows me to manage every detail of permissions per directory without needing a code break and a reboot of the main server's config file each time. Moreover, having been around for a long time, the community documentation is quite extensive; most bizarre routing or proxy issue that you encounter has likely been addressed and documented elsewhere on the web. Review collected by and hosted on G2.com.

It definitely can't compete with newer options such as Nginx, especially with respect to memory usage. Its process oriented design may make it a RAM consumer and drain it rapidly when the number of concurrent users suddenly surge. The main configuration files are also very unforgiving, and can at times be cumbersome to navigate through. When you edit the httpd.conf file, a minor mistake or a missing character on it may prevent the server to be restarted and finding out what is the exact spelling mistake can be very frustrating when you need to rush a deployment. Unlike my preferred choice of servicing heavy loads of static assets, it is also not my favorite. Review collected by and hosted on G2.com.