Apache Web Server (Apache HTTP Server) is an open source HTTP web server for modern operating systems including UNIX and Windows.
N/A
BIG-IP
Score 9.1 out of 10
N/A
F5 BIG-IP software from Seattle-based F5 Networks is a load balancing and application protection solution suite available on cloud or via virtual editions, on a subscription or perpetual licensing basis. The BIG-IP suite of products supports a wide range of security and application performance needs. The suite includes BIG-IP Local Traffic Manager (LTM) traffic management and optimization, BIG-IP DNS, BIG-IP Access Policy Manager (APM) identity and password protection, BIG-IP Application…
As I mentioned earlier, the Apache HTTP Server has a small disadvantage compared to the competition (NGINX) in terms of performance. If you run websites that really have a lot of visitors, NGINX might be the better alternative.
On the other hand, the Apache HTTP Server is open source and free. Further functionalities can be activated via modules. The documentation is really excellent.
The scale, performance, and configuration for various scenarios have already been mentioned. The versatility, reliability, etc., are dependable and well-known. Being the industry leader, it is almost a standard, and no one can get fired for recommending F5 compared to some of the new offerings, which are not battle-tested.
Street Cred: Apache Web Server is the Founder for all of Apache Foundation's other projects. Without the Web Server, Apache Foundation would look very different. That being said, they have done a good job of maintaining the code base, and keeping a lot of what makes Apache so special
Stability: Apache is rock-solid. While no software is perfect, Apache can parse your web sources quickly and cleanly.
Flexibility: Need to startup your own Webpage? Done. Wordpress? Yup. REST Endpoint? Check. Honeypot? Absolutely.
The default configurations which comes with Apache server needs to get optimized for performance and security with every new installation as these defaults are not recommended to push on the production environment directly.
Security options and advanced configurations are not easy to set up and require an additional level of expertise.
Admin frontend GUI could be improved to a great extent to match with other enterprise tools available to serve similar requirements.
I think the policy configuration that had some improvements on the ASM word things, improvements may be on the signatures that would be good because it's a little bit confusing on the ASL, how they are updated and deployed, and this staging. So that's something that could be.
I give this rating because there is so much Apache documentation and information on the web that you can literally do anything. This has to do with the fact that there is a huge Open Source community that is beyond mature and perhaps one of the most helpful to be found. The only thing that should hold anyone back from anything is that they can not read. RTFM, my friend. And I must say that the manual is excellent.
On the occasions when we've had to engage f5 support, they have been great. They have always resolved our issues quickly and been easy to work with and professional. The reason I give them a 10 out of 10, however, is because when we've had issues that have crossed over between the f5 BIG-IP, our Cisco switches, and our Microsoft IIS server the f5 support representatives have been extremely knowledgeable about every product and device involved and have been able to troubleshoot end-to-end without having to engage other vendors.
I has a lot more features, except that IIS is more integrated in a Windows environment. But now with .net core also possible from Apache it would work anywhere really. Only in a full Windows environment where full integration is needed I would chose to go for IIS. Otherwise Apache it is.
So the cloud versions, and admittedly we did not do the Imperva on-prem solution. We only went with cloud. There's a lot of idiosyncrasies, like you can't use real IP addresses, you must snap. And that caused us problems with DNS and DNS routing. So we had to turn on some features with F5 that did remediate the issue, like using the one connect profiles, but that did cause some other problems identifying traffic and we had to make some eye roll changes to use the exported four headers.
